Having to convert database from 2010 to 2003, wth global variables

[wakerider05]

Hi all,

I have an access database that has a “user login” section. When that user logs in, it stores their username as a global variable, so I can call it on other forms for security purposes.
Meaning If I log in as John Doe, and I fill out a form, there is an E Signature area that is automatically populated with John Doe.

However my client only has Access 2003, I saved the database as 2003 no problem, except I got an error on my forms that use the global variable that says it cannot save because of the module of the Global variables. I need some way to get the value of the logged in user into those forms that need the E-Signature.
Two questions:
Can I still use the global variable process?
What’s another way I can get them in their?


my glabal variables stored in a module:

Option Compare Database
Global gstruser As String
Option Explicit

than on the form i have the code
Text42.Value = gstruser


Thanks guys, I hope this makes sense.

[June7]

As far as I remember, Access 2003 accommadated global variables.

The alternative is to not use global variable and store the user login info directly to textbox on a form that never closes. That is what I do.

I tried global variables but was aggravated by them in debugging because if code execution is interrupted the variable loses value.

[Missinglinq]

...As far as I remember, Access 2003 accommadated global variables...

That's correct!

...I tried global variables but was aggravated...because if code execution is interrupted the variable loses value...

Also true! The new TempVars, introduced in 2007, supposedly resolved this problem.

Conversion , especially backward conversion, often has hiccups. I wonder if the problem doesn't lie with how you're setting the value of the Variable, rather than with the line

Text42.Value = gstruser

The syntax for doing some things, especially those associated with using Envir(), and such, changed between 2003 and 2007, I believe.

Linq ;0)>