Same time multiuser database - Access 2003

[Julian]

Is it possible to access (write) a database by more than one user at the
same time in Access 2003? I've tried that and got a warning message saying
whether I want to save the other user records and lose mine or overwrite the
other ones. One user was on the PC where the database resides and the other
one was accessing it via network.
Julian

 

[Guest]

I am assuming that you are talking about using the database and not creating
an application.
If so then the answer is yes. Use a split database where each user has their
own frontend that has the forms, queries, and reports, in it which accesses a
backend that houses the data tables.

Query this forum for "split database" and you should get plenty of info.

Regards,
Nick.

 

[Guest]

yes it is! maybe that you and the other user are trying to edit the same
record at the same time. you should communicate with the other user to know
what he is editing.

 

[Guest]

Hi Julian,

Yes, it most certainly is possible. Please see the following article:

Implementing a Successful Multiuser Access/JET Application
http://www.access.qbuilt.com/html/multiuser_applications.html

The warning message you received is due to two users attempting to edit the
same record at the same time. That is something that is not possible with JET
(Access) databases. You should split the database into what is commonly
referred to as a front-end (FE) file and a back-end (BE) file. There is a
hyperlink in the above article that explains more about splitting.

One user was on the PC where the database resides and the other
one was accessing it via network.

This is definately not an optimum setup, because the server PC in this case
is going to be busy with whatever the person is doing on their PC that has a
copy of the database. The client will be waiting longer for time slices. If
possible, the back-end should be copied to a folder on a file server PC. Each
client PC should have their own copy of the FE file.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[David W. Fenton]

This is definately not an optimum setup, because the server PC in
this case is going to be busy with whatever the person is doing on
their PC that has a copy of the database. The client will be
waiting longer for time slices. If possible, the back-end should
be copied to a folder on a file server PC. Each client PC should
have their own copy of the FE file.

Oh, come on. It works fine to use a peer-to-peer setup with small
numbers of users. I've had a client running 3 users in a database
with the back end stored on one of the workstations (the workstation
of the user who does the most work). It's not slow and it's not
fragile.

Remember that many small offices don't *have* a dedicated server.

Indeed, that would include at least half of my clients.

 

[aaron.kempf]

CORRECTION:

Remember that many OF DAVID's small offices don't *have* a dedicated
server.

Don't be egocentric, all of my clients have a server

-Aaron