matsumotod
asked on
Unknown error on Environ("Username")
I have a database in Access 2002-2003 format. One form has a field where the table-level default is the expression =Environ("Username"). This field relates to another table (lookup wizard, limited to the list values), where the username is the primary key for users' contact information. Other than startup restrictions, the database has no other security (user-level, encryption, etc.).
When I test the database from my local hard drive and from a shared network drive, I have no problems. However, from the shared network drive, when other users try to open that form (I've tested with two other users), they get the application message, "There was an error executing the command". However, I still have no problems.
From another question on this site, I tried replacing =Environ("Username") with the function at http://www.mvps.org/access/api/api0008.htm. However, those two other users still get the same message, but I still have no problem. Thus, I don't think it's the function causing the error. Also, I checked the spelling of the usernames in the related table, and they are correct.
I would say it's some kind of difference between me and the other two users, but we all work for the same company and run off identical systems (Windows XP and Office 2003) with all the same updates and patches.
What could be causing this?
When I test the database from my local hard drive and from a shared network drive, I have no problems. However, from the shared network drive, when other users try to open that form (I've tested with two other users), they get the application message, "There was an error executing the command". However, I still have no problems.
From another question on this site, I tried replacing =Environ("Username") with the function at http://www.mvps.org/access/api/api0008.htm. However, those two other users still get the same message, but I still have no problem. Thus, I don't think it's the function causing the error. Also, I checked the spelling of the usernames in the related table, and they are correct.
I would say it's some kind of difference between me and the other two users, but we all work for the same company and run off identical systems (Windows XP and Office 2003) with all the same updates and patches.
What could be causing this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I think I figured it out - it was two-fold. First, I did need to take the function out of the table default. Second, I had to disable "sandbox mode" on that function - see http://www.access-programmers.co.uk/forums/showthread.php?t=76173.
ASKER
I don't know what an API function is, so a little more on my setup - there's a main "Courses" table, that has a few lookup fields related to three other tables' records via the primary keys. The "Participant" lookup field is related to the "People" table, where the username is the primary key. The default for "Participant" is the =Environ("Username"). I've created a query that is basically a duplicate of the "Courses" table. However, the query criteria is set to be =Environ("Username") for "Participant". This query feeds a form for data entry (both editing current records and adding new ones), where the "Participant" field is disabled - that is, the users can see that they're being identified as the participant, but they can't change it.