DWUTKA at marlow.com
DWUTKA at marlow.com
Sat Nov 26 23:27:19 CST 2005
Or pressing the stop button. Drew -----Original Message----- From: Gustav Brock [SMTP:Gustav at cactus.dk] Sent: Saturday, November 26, 2005 1:01 PM To: accessd at databaseadvisors.com Subject: Re: [AccessD] Public Variables - Scope and Lifetime Hi Drew That's right, but perhaps you should mention that you _stop_ the code by the command END. Command STOP only pauses it ... /gustav >>> DWUTKA at marlow.com 26-11-2005 19:42:23 >>> Ugh....not this again! LOL. Marty, that is not what happens. If you STOP your code, then everything gets reset. That does include your global variables. It's not a maybe, and they don't 'lose' their values, the code is stopped. It is just like stopping an .exe, all values in memory are cleared. The difference is, with Access, that the Access Shell didn't stop, and as soon as you do something requiring code, Access starts it all up again, and so your Globals will be reset. It's not a wishy washy thing, it is just how the code works. Drew -----Original Message----- From: MartyConnelly [SMTP:martyconnelly at shaw.ca] Sent: Saturday, November 26, 2005 10:51 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Public Variables - Scope and Lifetime If you go into Debug mode with global variables. They maybe reset or lose their values.. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com