Additionally, locks need to be at the "single-record" level, so that others can be working with
different recods.
To add to Dirk's answer, please see the following KB article:
PRB: Jet 4.0 Row-Level Locking Is Not Available with DAO 3.60
http://support.microsoft.com/?id=306435
Tom
_________________________________________
Access 2002 certainly does allow multiple concurrent r/w users. Be sure
that (a) the Access "Default Open Mode" option is set to Shared, not
Exclusive, and (b) all users have full privileges (incuding delete
privileges) on the folder containing the database.
You can set the Default Record Locking option to "Edited record" if you
want, though for most purposes the "No locks" setting is adequate:
users only conflict when two or more users have edited the same record
at the same time, and one saves before the other -- then a
write-conflict message is displayed.
Note, however, that when sharing a database it is best to split the
database into a "back-end" .mdb file containing only the tables and a
"front-end" file containing all the other objects -- queries, forms,
reports, macros, modules -- with tables that are linked to the back-end
tables. Then give each user his own copy of the front-end. That
minimizes network traffic and the risk of project corruption due to
network glitches.
--
Dirk Goldgar, MS Access MVP
www.datagnostics.com
(please reply to the newsgroup)
_____________________________________
We have a database that requires multiple users to R/W simultaneously. I've seen that Access 2002
only allows a single user in the database at a time. Is that indeed the case, and if so, is there
any way around it? If not, how can I enable a database for multiple concurrent users.
Additionally, locks need to be at the "single-record" level, so that others can be working with
different recods.
Any assistance in this would be greatly appreciated.
