[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