[AccessD] Kicking and screaming

Ha, SysVars are nothing new. 

I have been working with a legacy Informix application (20+ years old) and
once you have pushed a variable up into memory they are there until you
leave the environment completely...very handy at times as you move from
module to module or even from program to program or more likely crashing
while doing development work. There is even an option that allows protected
variables to be pushed to the computers stack...but this doesn't work on the
newer computers with their fancy new-fangled multi-core CPUs 

I have always, when working with VB, pushed and retrieved variables out of
the system register. They are then totally protected until a system
re-imaging and even then can be pulled from backup. Somewhere, I have a
little piece of code I used with Access to perform similar efforts.

It is nice to hear that MS Access is finally catching up. :-)

PS: Good to hear you are doing OK.

Jim    

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John W Colby
Sent: Tuesday, January 22, 2013 5:59 AM
To: Access Developers discussion and problem solving
Subject: [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

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

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com