Originally Posted by
StolenDog
...I am trying to set up a simple database that will be used by six or seven staff members simultaneously. I am using Access 2007 on a network drive (windows XP)...
Originally Posted by
StolenDog
...but how do I tie the user in access to the company database...
I suspect that the answer to the second quote is directly related to the first quote!
It sounds suspiciously like you are you trying to have all employees use a single, non-split copy of this database that resides on the network drive? Is this the case? If so, you need to address this before you do anything else!
Having multiple users sharing a single, non-split database, sitting on a network drive, is the sure way to repeated episodes of corruption, as well as speed and timing problems! Multiple users simply have to work off of a split database, with each user having their own copy of the Front End, which contains everything except the data/tables, on their respective hard drives, and a Back End with only the Tables on a shared drive.
Being in forced retirement, I spend 8-10 hours a day here and on other Access forums/newsgroups, and over the past ten years have seen dozens and dozens of reports of non-split apps causing these kind of problems! The really insidious thing is that a non-split app can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again!
Once each user has their own copy of the Front End, pulling their individual Windows ID will be a snap...and the business of no one being able to do anything will probably be resolved!
Here are two tutorials on Splitting a Database:
https://www.fmsinc.com/microsoftacce...abaseSplitter/
http://www.hitechcoach.com/index.php...atid=24:design
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007