Stuart McLachlan
stuart at lexacorp.com.pg
Tue Jan 22 15:39:13 CST 2013
What Gustav says ! :-) Tempvars are just a fancy OO was to store Globals. (They are objects with two members - Name and Value). Ther is nothing built in like the Sysvars we have built ourselves for years. -- Stuart On 22 Jan 2013 at 15:28, Gustav Brock 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 >