I created some Public variables using Access 97 to hold often used database options.
One example is a variable to test for debugging mode, so the code can make special considerations for printing debugging code, etc.
The variables are set in the top of a module, before any Procedures with this kind of syntax:
Expand|Select|Wrap|Line Numbers
- Public bDBUGGING as Boolean
In Access 97 it works fine. The value stays in the public variable in between actual testing runs, while I am coding, etc. Then when code is ran it finds the values previously set, either by hand or in VBA code.
When I try to use this in Access 2003 however, it acts different. It holds the value while the code is executing but then loses the value when execution finishes.
Is there any way in 2003 to configure the database to keep the value between code runs? For example, when you are just sitting at a menu, the VBA is not executing, and then you click a button that uses the this value.