General - Save user login in a table

This may be a stupid question to ask, but I am working with Access for the first time, so any help is appreciated.

The db that I created is a simple one, it tracks upwards of 1000 "totes" as they move from one location to another. I am going to have about 200 users entering data from over 30 different locations.

I need to track who enters each record. I am setting up security and permissions now, so each user will have to log in to do enter data. When they login, is their username stored somewhere were you can recall it and add it to a record? Currently I have a text box in nearly every form that they have to enter their name in. I would like to remove that and automate it with their username - behind the scene if you will.
Any assistance is appreciated....

first of all, how many cocurrent users will there be? Anything over around 25-30 will lead to lockout errors and database corruption. Secondly, there are modules out there that will pull up the username on the database, use that as part of your data-entry form, and you can date/time stamp to boot. I have used the modules before, to great effect. It's past my bedtime right now, but tomorrow I can give you a link to such a module. To be honest though, 200 might be way over MS Access's ability, unless there will only be 10-20 connected at any given time. The username part is easy...... the data base corruption is not.

I would be even more pessimistic than sbenj69, I would say forget it, if you might have more than about 6 simultaneous users, and that's only if you split the database, with one common "back-end" .mdb containing the data tables, and everyone has their own copy of the "front-end" .mdb containing the queries, forms, reports, etc.

Several other factors are involved, too. Will all users be on the same local network? (You mentioned "different locations".) And is the network a reasonably high-speed network?

Access is a fantastic database engine and development platform for single users, or a small number of users under good network conditions and with a suitable system design (split database). It can cause you grief like you don't want to know about when inexperienced people try to use it in the wrong environment. You probably should be thinking in terms of SQL Server, the "older brother" product from Microsoft. There is an Express edition that is now a free download from Microsoft. You might want to consider that.