client/server setup

[J. Freed]

I'm trying to set up a client/server application where multiple people will
be simultaneously editing a single table. (Each user will be restricted to
only those records belonging to him and there should be no overlap).

I know how to create the client and server pieces but I'm not sure what I
might need to do to allow the multiple simultaneous read/write access. Any
ideas? TIA.

 

[John W. Vinson]

I'm trying to set up a client/server application where multiple people will
be simultaneously editing a single table. (Each user will be restricted to
only those records belonging to him and there should be no overlap).

I know how to create the client and server pieces but I'm not sure what I
might need to do to allow the multiple simultaneous read/write access. Any
ideas? TIA.

Access is multiuser, out of the box. You don't need to do all that much!

Use a "Split" database: the table (or tables) should be in a shared "backend"
database, and each user should have their own copy of a "frontend", containing
the forms, queries, reports and code, linked to the backend. You can use
Tools... Database Utilities... Database Splitter Wizard to split it for you.
For an extensive discussion see
http://www.granite.ab.ca/access/splitapp.htm

 

[Bernard Peek]

I'm trying to set up a client/server application where multiple people will
be simultaneously editing a single table. (Each user will be restricted to
only those records belonging to him and there should be no overlap).

I know how to create the client and server pieces but I'm not sure what I
might need to do to allow the multiple simultaneous read/write access. Any
ideas? TIA.

Access is a database management system. It can handle shared access to
data from multiple clients. Having said that, its multi-user
capabilities are limited so if you have many simultaneous users you
should consider using a different solution, such as an SQL Server
database.

How many simultaneous users do you expect?