So, I've come to find that the problem I had earlier was caused by using the
end statement, which clears the value of all variables upon it's execution.
Can anyone suggest a way to Set all variables in the auto_open macro in such
a way that their values will be maintained after code execution stops? I
would like to avoid copying all the set statements I use to each
procedure... But I suppose I will if I've got to :)

-Mike-hime

If you declare your variables as Public in the General Declarations (not within a module) the values will be retained after the code runs.

ie

Public SomeVariable as Integer

Sub Some_Sub()
--Your code here
end sub

Hope that gets you what you need.
TerryK

I was under the impression that you are correct... but even though I have
coded it that way, after I run a procedure if I try to run it agian, it will
cause an error saying that my variables aren't defined. It seems buggy to
me.

"TerryK" wrote in message
...
If you declare your variables as Public in the General Declarations (not
within a module) the values will be retained after the code runs.

ie

Public SomeVariable as Integer

Sub Some_Sub()
--Your code here
end sub

Hope that gets you what you need.
TerryK

Are the variables declared in the same Module or UserForm as the code that is refering to them
If not you might need to qualify them more strictly. for exampl

SomeUserForm General Declaration
Public SomeVariable as Intege

---------
Module

Sub SomeSub(
x= SomeUserForm.SomeVariabl
end su

I agree it seems buggy sometimes, I have found it best to be as explict as I can when calling variables and procedures. The small amount of extra typing gets rid of lots of unexplainable surprises

TerryK