I hope someone can suggest a way around a seemingly intractable problem. I have database that opens a form (frm_progress) from which the user selectes an area (North, South, etc) from a combo box (Combo13). This area is then used to point the subsequent VBA, SQL queries, Forms and Reports to the relavnt data tables. I would like to store the value of the combo box in a variable that is available to all modules (Class or otherwise). I have tried

Public Const area As String = Forms!frm_progress!combo13

but, of course, that is rejected. I am sure there MUST be a way to do it rather than putting 'area = Forms!frm_...' etc in each module after declaring 'Public area as String'

Can anyone help?

Hi
Declare a public variable named Area
Then in Combo13 AfterUpdate event assign value to Area Variable

Public Area As String

Area=combo13

-vemaju

I always find it good to declare all my global variables at the top of a module, outside of any function or sub procedure. This just helps me keep them all together and controlled - well as much control as you can have with a global variable. Vemaju is right on the money!

Mike
EchoVue.com

Thank you both. When it's written down, it's obvious - it just necer occurred to me that when you set a global variable, it's value remains set. Back to school for me, i think

Hi
It is a good practice to have one module in your project, where you declare all public constants and public variables and nothing else.
I always name this module with name Globals

-vemaju

Hi,

   This discussion is very instructive. Can you tell me more about what the code in the module would look like that would take the value from the combo13 after update event?

Thanks,




mmcdonal

The Global variable would be declared in the Globals module, however the value would need to be assigned based on some event. You could just have a on onClick even associated with the combo box and then set that value = to your Global Variable. The Global variable is initialized when the application is started and is available from anywhere in the application...

This brings up an interesting problem though. While Global variables definitely make life a little easier. In programming circles particularly with the advanced object oriented languages like Java, the belief is that Global variables should be avoided where ever possible. The reason being that because the variable is accessible from everywhere, in complex programs, you run the risk of the value not being updated or being changed while the variable is 'en-route' to where you intend to reference it.

Mike

Mike
EchoVue.com