Jim Lawrence
accessd at shaw.ca
Mon Mar 24 16:37:19 CDT 2014
Hi John: Good point but today's reality is that virtually all (or all) data systems are asynchronous. This means unbound. By the end of the nineties the whole concept of bounds objects was irrelevant. There just is enough server farms or broadband networking to support bound networks. Bound type databases networks because of this technology are very limited in size and with creation of fully capable ACID databases, unnecessary. In all databases the only thing that the desktop needs to manage is changes, deletions and additions. How the back-end handles all that is not a FE concern. That is why the MDB should never be used in place of real database work as it simply does not have the capabilities of a real SQL DB....and needed to have bound data in order to function...it was dead tech as of twenty years ago. Love your classes though and as soon as you have a fully function set of MS Access classes that support asynchronous databases count me in. Jim ----- Original Message ----- From: "John W Colby" <jwcolby at gmail.com> To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Sent: Sunday, March 23, 2014 7:52:10 PM Subject: Re: [AccessD] Unbound Form Check For Changes Jim, >I see no flaw in your argument other than, if you don't already have classes built and tested, it can be a bit of over-complexing a rather simple requirement. You consider unbound forms a "rather simple requirement"? I build a framework (and I have built several) one piece at a time. A journey of a thousand miles begins with the first step. To never take the first step guarantees that the journey remains nothing but a dream. I have a blog which builds very basic classes, and explains how and why they work. http://jwcolby.blogspot.com/?view=sidebar It is not copyrighted. And contrary to popular belief, it isn't rocket science either. John W. Colby Reality is what refuses to go away when you do not believe in it On 3/23/2014 10:35 PM, Jim Lawrence wrote: > Hi John: > > I see no flaw in your argument other than, if you don't already have classes built and tested, it can be a bit of over-complexing a rather simple requirement. For larger projects, a healthy code library, at your disposal, is of course now a requirement. > > Jim > > ----- Original Message ----- > From: "John W Colby" <jwcolby at gmail.com> > To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> > Sent: Sunday, 23 March, 2014 6:54:51 PM > Subject: Re: [AccessD] Unbound Form Check For Changes > > LOL, but you have already made clear that you see no benefit to classes in general. > > Classes allow us to use Object Oriented programming techniques. The programming language / > environment is irrelevant, that is their purpose. > --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com