How to allow multiple users to enter data simultaneously?

A

Avery

I have a database with several tables and I would like to allow more than one
person to be able to enter data (mind you, on different tables)
simultaneously -- is there a way to accomplish this? It seems as if earlier
versions of Access allowed for this however with Access 2003, it will only
let one person make changes and for anybody else it is "read only"
 
D

Douglas J. Steele

The application should be split into a front-end (containing the queries,
forms, reports, macros and modules), linked to a back-end (containing the
tables and relations). Only the back-end should be on the server: each user
should have his/her own copy of the front-end, ideally on his/her hard
drive.

Each user must have a minimum of Read and Write on the folder where the
back-end file exists. (It's usual to give them Delete permission as well).
This is because Access will create a locking file (.ldb) in that folder when
the first user connects. As each subsequent user connects, Access will
update the locking file. When the last user disconnects from the back-end,
Access will attempt to delete the locking file.

I've heard of some cases where the folder permissions were set up
incorrectly so that users were able to create the locking file, but could
not update locking files created by other users. They must be able to, or
they won't be able to make updates to the database.
 
A

Arvin Meyer [MVP]

You must split the database and have the front-end with the forms, queries,
reports, and code linked to the data tables in a back-end on the server. The
server share must have all permissions with the exception of Full-Control.
Without Create and Delete permissions, the user cannot create or delete the
locking file (.LDB) which is necessary for multiple users.
 
D

David W. Fenton

You must split the database and have the front-end with the forms,
queries, reports, and code linked to the data tables in a back-end
on the server. The server share must have all permissions with the
exception of Full-Control. Without Create and Delete permissions,
the user cannot create or delete the locking file (.LDB) which is
necessary for multiple users.

Delete permissions are *not* required. If you omit them, your LDB
file will work just like it did in Access 2, i.e., it survives the
last user logout instead of being deleted.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top