[AccessD] Open Multiple Instances of a Form and passing aparameter

 > but it saves a lot of time in wiring up new forms to basic functionality.

Yep, and it makes things standardized.

You can take my class and instantiate it in your own form class so that as the form opens and your 
own custom class instantiates, it grabs any Openargs, parses them and they are available to your 
class and your form code to use.

The nice part of the class way is that suddenly every form has a standard set of functionality.  No 
more what I will call "JIT programming".  ;)



John W. Colby
Colby Consulting

Reality is what refuses to go away
when you do not believe in it

On 8/7/2012 10:53 AM, Charlotte Foust wrote:
> John,
>
> I'm a believer in classes too.I don't have a framework built so for this
> contract, I whipped up a form class to handle stuff I wanted standardized
> in all my forms without having to rewrite the code in every form (I'm only
> up to about 30 forms so far, so it's not critical, just a very big help).
> Of course you still have to turn on the shell of the routine in the forms
> because of Access's peculiarities, but I can handle things like the msgbox
> letting the user know that the current record can't be saved and asking
> what to do with it the same way in every form without copying and pasting.
> There's plenty of code in each of those forms, so they don't miss having a
> few things offloaded to a central class.  Mine isn't pure class usage
> because I'm in a tearing hurry (can you say "contract"?) to make it work,
> but it saves a lot of time in wiring up new forms to basic functionality.
>
> Charlotte