[AccessD] Feeding an paramarray to a paramarray

Drew Wutka DWUTKA at Marlow.com
Wed Mar 12 16:13:55 CDT 2008


Ok, a little off the original topic, but you shouldn't hard code
permissions in code, because changing permissions then require code
change.  Instead, have the user's groups in a table, and the form's
groups in a table, and have the two collections compare each other.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Wednesday, March 12, 2008 3:52 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Feeding an paramarray to a paramarray

that is exactly what it is for and when it is needed it works well.  For
example I so stuff like allowing a form open for a set of Groups in my
security.  Thus in the form's OnOpen I call a function and pass in all
the
groups that are allowed to open the form.  If the currently logged in
user
is in any of those groups the form stays open else the cancel is set and
the
OnOpen is exited.  There is no way in advance to know what specific
groups
can open the form, it is hardcoded in the open event of each form.

In cases like that it works quite well.  

John W. Colby
Colby Consulting
www.ColbyConsulting.com 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
Sent: Wednesday, March 12, 2008 4:35 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Feeding an paramarray to a paramarray

I hear ya. Not sure where I would use a ParamArray in stuff I do now
anyways.  It's a neat idea, but it seems that it is really designed to
allow
you to have multiple arguments to a function, without having to define
them.

Most of my logic is done in classes now, any functions I use are pretty
straightforward, no need to be all that flexible.

Drew

The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI Business Sensitive material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.





More information about the AccessD mailing list