[AccessD] Kicking and screaming

I use TempVars. They are created when the file is opened and changed as
needed during the session.
They are in memory until they are either destroyed or when the file is
closed.
One example is I use one for the role of the individual that logs into the
database.
The role determines what the user can see and / or do during the session.
Prior to using TempVars I was constantly referencing a table using
DLookup()... it wasn't very efficient.
Now all I have to do is something like:  TempVars!tvRole = something - a
lot easier.

Jim
On Tue, Jan 22, 2013 at 8:28 AM, Gustav Brock <gustav at cactus.dk> wrote:

> Hi John
>
> You may have TempVars in mind - but given that name, how can they be
> persistent?
> Stick with your SysVars.
>
> Thought you had left the list, but struggling with A2007 may explain a few
> things. Why do you do this to yourself?
>
> /gustav
>
>
> -----Oprindelig meddelelse-----
> Fra: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] På vegne af John W Colby
> Sendt: 22. januar 2013 14:59
> Til: Access Developers discussion and problem solving
> Emne: [AccessD] Kicking and screaming
>
> OK, I am immersed in Access 2007 now.  Sigh.
>
> Aaahhhhooooooommmmmm this is what I do for a living.
> Aaahhhhooooooommmmmm this is what I do for a living.
> Aaahhhhooooooommmmmm this is what I do for a living.
>
> Now that I am centered again... I have heard that Access now has built-in
> what I have always called SysVars and programmed a solution for, a table /
> code for system variables which need to be stored in a table and loaded at
> startup.  Is this true?  Where do I find documentation on using it?
>
> --
> John W. Colby
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>