I guess we should take a step back.
Does each user work on information about one and only one location?
If so, that is the easiest scenerio. You can create a user profile table and
place the location id in there and use the user's user id as the key.

You may already have a user profile table to store other information about
the user. Full name, department name, printer preference, security or
authorization level or ?

Once they have signed into the PC, there is no need to seperately sign into
Access. Access can determine the login userid.

John.. Visio MVP


"CorporateQAinTX" wrote in
message ...
Now this is what I was looking for...options and less forms.

The users have to sign in to the computer, but not into Access. Now, I
have
been tinkering with user-level securities so I can require each location
to
sign in. I just don't understand how to "tie" the location id to the user
log-in. Technically the user can open the db from any computer linked to
our
network. Our corporate server is accessible from each of our facilities.
They
can read from certain folders and write to even fewer. The main db will be
hidden in one of the folders they can read from and each facility will be
given a shortcut with the /runtime and /wrkgrp lines embedded in it. The
problem in the past is that we have too many people who like to tinker
instead of calling the DB Administrator. Anyway, the login's aren't
session
based. Do you think you can help me John?

Thanks for clearing my head and helping me out of a big mess.

"John... Visio MVP" wrote:

"CorporateQAinTX" wrote in
message ...
John, I profusely apologize for my ignorance.

No apologizing is necessary, you just fell into a trap.

John, Fred, while you've been helping me to see the error of my ways,
did
either of you happen to consider whether Steve's assessment of my
situation
was correct or not?

The single table with a location id is the way to go, but contrary to
what
steve suggested, use a single form with the location id hidden.

Now the trick is determining how you want to set the location id. Of
course
there are a few other questions to ask before you decide on a solution.
1. If the users are required to sign in, you can tie the location id to
their profile.
2. Can a user enter information from more than one location? Possibly
linking the Location id to a menu selection is the way to go.
3. If they can enter information from more than one location, is it
session
baed. Then the point at which you switch sessions can set the Location
Id.

Thanks folks, and I'm sorry if I may have offended anyone.

No offence taken.

John... Visio MVP