client/server setup

[J. Freed]

I'd like to create a client/server application where multiple users can
read/write access a single table, each user accessing a unique portion of the
table. If I create a link to the table in each copy of the client database,
would there be a problem with multiple simultaneous users editing the table?
TIA....

 

[Bernard Peek]

I'd like to create a client/server application where multiple users can
read/write access a single table, each user accessing a unique portion of the
table. If I create a link to the table in each copy of the client database,
would there be a problem with multiple simultaneous users editing the table?
TIA....

Are you sure that what you are looking for is a client/server system,
that's a specific technical term with limited applicability to Access.

However if you create a query on the server for each user and restrict
each query to one person's data, you can link each client to a different
query. This could get very complex if you have many users. It's possible
to simplify this by using some VBA code, provided you have sufficient
VBA skills.

 

[John W. Vinson]

I'd like to create a client/server application where multiple users can
read/write access a single table, each user accessing a unique portion of the
table. If I create a link to the table in each copy of the client database,
would there be a problem with multiple simultaneous users editing the table?
TIA....

There is a limit of 255 simultaneous users accessing a database. In practice,
things can get dicey if you have more than 30 or 40 users *SIMULTANEOUSLY
EDITING* (not just viewing) the database, and you will have problems if two
users try to simultaneously edit the same record.

How many "multi" users are you talking about?
Are they all on the same fast stable LAN, or are you talking about one user
from Tokyo and another from Poughkeepsie?

More info please!