Environ$("USERNAME") not working on some computers

  • Thread starter Thread starter AimeeK via AccessMonster.com
  • Start date Start date
A

AimeeK via AccessMonster.com

Hi, I'm using Environ$("USERNAME") to get the network login for whomever is
using a database, and some of the users are getting a NAME#? error. Would
this have anything to do with the version of Windows they're using?

Thanks.
 
AimeeK via AccessMonster.com said:
Hi, I'm using Environ$("USERNAME") to get the network login for
whomever is using a database, and some of the users are getting a
NAME#? error. Would this have anything to do with the version of
Windows they're using?
Click to expand...

It probably has to do with what Jet service pack they have installed,
and whether sandbox mode is enabled or not:

http://support.microsoft.com/kb/239482/en-us
How to configure Jet 4.0 to prevent unsafe functions
from running in Access 2000 and Access 2002
 
Dirk, Thank you for replying...I did manage to get the fosUserName module to
work, so I'm using that in place of Environ$("USERNAME"). However, I'm just
wondering if they'll have that same problem if the incorrect version of the
Jet service pack is installed. Thanks again.
 
AimeeK via AccessMonster.com said:
Dirk, Thank you for replying...I did manage to get the fosUserName
module to work, so I'm using that in place of Environ$("USERNAME").
However, I'm just wondering if they'll have that same problem if the
incorrect version of the Jet service pack is installed. Thanks again.
Click to expand...

fOSUserName() is more reliable than Environ$, anyway. I don't see why
it should be affected by any Jet service packs.
 
Back
Top