Jason,
Did you ever hear the one about the guy cutting a huge pile of wood with a dull saw? His foreman walked by and asked him why he hadn't sharpened his blade all day. The guy replied, "I can't stop, I've got all this wood to cut."
Yes, you can have several people access one database from your server. But the phenomenal headaches you'll deal with in the form of corruption, having more trouble getting out new versions to users (_definitely_ not less), and dealing with other hassles will, in _very_ short order show you why every professional access developer insists on splitting databases into front ends and back ends, using a custom process to roll new versions out to users as needed, and taking proper care with their databases.
One of the things you'll get used to as you develop more and more access databases, or do any other sort of programming, is that a large part of your job is making decisions about when it is better to put more time into automating a process and when it is best to leave things as they are. In this case, thousands of developers have faced the same issues you are, and every one of them eventually realizes that it is best to put a good bit of energy into creating safe environments for their users, and that a big part of this is, and one that is not even up for discussion, is splitting their databases into front end and back end.
The Deploying Databases section of my website lays out the way I go about rolling out new versions to users. There are plenty of other rock solid ways to do this out there. Find one, learn it, use it. You users and your supervisors will all thank you.
Jeremy
==
Jeremy Wallace
AlphaBet City Dataworks
Affordable Development, Professionally Done
Please post in the appropriate forum with a descriptive subject; code and SQL, if referenced; and expected results. See thread181-473997 for more pointers.