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

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

On Tue, Aug 7, 2012 at 7:14 AM, jwcolby <jwcolby at colbyconsulting.com> wrote:

> Goto
>
> http://www.databaseadvisors.**com/downloads.asp<http://www.databaseadvisors.com/downloads.asp>
>
>
>
> Years ago I posted an example class for how to parse OpenArgs.  Of course
> once I am passing in OpenArgs like this I (personally) wanted to be able to
> pass in arguments specifically destined for writeable properties such as
> Caption, Locked, Visible, AllowEdits and so forth.  So my class (which I
> actually use in my Framework) also can be told to check the openargs for a
> specific list of properties and if the VarName is the same as any of the
> settable properties, then place VarValue into that property.
>
> So my example includes code to do that, however if you don't care about
> such functionality you can ignore it or even strip it out.
>
> Classes are not rocket science, and they allow us to write and debug
> blocks of functionality that make sense and that we want to use over and
> over.
>
>
> John W. Colby
> Colby Consulting
>
> Reality is what refuses to go away
> when you do not believe in it
>
> On 8/7/2012 8:35 AM, Heenan, Lambert wrote:
>
>> Exactly. A single Split statement will do it all, so why the need for a
>> whole class to do the job?
>>
>> Lambert :-)
>>
>> -----Original Message-----
>> From: accessd-bounces@**databaseadvisors.com<accessd-bounces at databaseadvisors.com>[mailto:
>> accessd-bounces@**databaseadvisors.com<accessd-bounces at databaseadvisors.com>]
>> On Behalf Of Rocky Smolin
>> Sent: Monday, August 06, 2012 9:20 PM
>> To: 'Access Developers discussion and problem solving'
>> Subject: Re: [AccessD] Open Multiple Instances of a Form and passing
>> aparameter
>>
>> I parse multiple arguments in a single string using the Split statement -
>> works a treat.
>>
>> Rocky
>>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/**mailman/listinfo/accessd<http://databaseadvisors.com/mailman/listinfo/accessd>
>
>
> Website: http://www.databaseadvisors.**com<http://www.databaseadvisors.com>
>
>
>