Same time access
- Thread starter dl41001
- Start date
- Local time
- Today, 11:00
- Joined
- Aug 30, 2003
- Messages
- 36,274
Of course. Since you have multiple users, you should be using a front end/back end set up where each user has their own copy of the front end on their PC, and the back end is on a server or other central location. Each user should be able to run the same report at the same time.
- Local time
- Today, 14:00
- Joined
- Feb 19, 2002
- Messages
- 47,859
It doesn't matter whether the users share a single .mdb located on a server or have individual front ends located on their local workstations. Any object can be simultaniously opened by another user. The objects are opened in memory on the client workstation so there is no conflict. If multiple users attempt to change the same record at one time, Jet detects the situation and gives one (or more) of the users an error message with three options as to how to resolve the update conflict - discard, overlay the other person's changes, or copy to clipboard and decide later.
I don't know what you want instruction on either. There is nothing you need to do to make a db sharable since that is the default behaviour.
I don't know what you want instruction on either. There is nothing you need to do to make a db sharable since that is the default behaviour.
- Local time
- Today, 13:00
- Joined
- Feb 28, 2001
- Messages
- 30,725
The only time that you would have problems with folks not being able to share the database is if you didn't set up Workgroup Security correctly.
What you need to do is to secure the database by creating accounts for each approved user. For each of these users, the only thing you need to assure is that they don't have Open Exclusive rights on the database. That is the ONLY possible reason that a database on a shared directory would not be shared properly - Open Exclusive would prevent any but the first user from being able to get to the database. And by default, users who don't join a properly set-up workgroup come in as Admin, who DOES have the ability to Open Exclusive.
Once you fix that problem, you should be good to go. Search this forum for topics Workgroup Security and Workgroup Setup and the like. You will find tons of articles. Heck, between me and Pat Hartman, that's probably 50 articles right there.
What you need to do is to secure the database by creating accounts for each approved user. For each of these users, the only thing you need to assure is that they don't have Open Exclusive rights on the database. That is the ONLY possible reason that a database on a shared directory would not be shared properly - Open Exclusive would prevent any but the first user from being able to get to the database. And by default, users who don't join a properly set-up workgroup come in as Admin, who DOES have the ability to Open Exclusive.
Once you fix that problem, you should be good to go. Search this forum for topics Workgroup Security and Workgroup Setup and the like. You will find tons of articles. Heck, between me and Pat Hartman, that's probably 50 articles right there.
Similar threads
