Does the Jet Engine provide true concurrent user access?

[Guest]

I'm getting conflicting info about multi-user, concurrent access to a .mdb
database. Assuming I'm using a shared folder on a network server, can other
Access users on that network engage in updating activities according to the
locking strategy I've chosen? I don't want to use the replication strategy
and I'm not ready to set up a client-server strategy based upon SQL Server.
Given 3 or 4 users and low volume of transactions, will a single .mdb file
work resonably well? Thanks

 

[Todd Shillam]

I have a client-server application built using Microsoft Access that handles concurrency just fine amongst a dozen users. I have the back-end (tables) on a network share; meanwhile, I have the application itself installed on each client. I have not had any problems. Not to mention, the data is transversing on a network that only supports 16 Mbps--still no problems at all.

Best regards,

Todd Shillam
I'm getting conflicting info about multi-user, concurrent access to a ..mdb
database. Assuming I'm using a shared folder on a network server, can other
Access users on that network engage in updating activities according to the
locking strategy I've chosen? I don't want to use the replication strategy
and I'm not ready to set up a client-server strategy based upon SQL Server.
Given 3 or 4 users and low volume of transactions, will a single .mdb file
work resonably well? Thanks

 

[Joseph Meehan]

I'm getting conflicting info about multi-user, concurrent access to a
.mdb database. Assuming I'm using a shared folder on a network
server, can other Access users on that network engage in updating
activities according to the locking strategy I've chosen? I don't
want to use the replication strategy and I'm not ready to set up a
client-server strategy based upon SQL Server. Given 3 or 4 users and
low volume of transactions, will a single .mdb file work resonably
well? Thanks

If you have not set up a split database with a back end and front end
you can expect problems, especially if someone likes to log on in exclusive
mode.

Properly set up I have had over fifty users set up without problems, but
I seldom had more than around twenty logged on at any one time.

 

[Rick Brandt]

I'm getting conflicting info about multi-user, concurrent access to a
.mdb database. Assuming I'm using a shared folder on a network
server, can other Access users on that network engage in updating
activities according to the locking strategy I've chosen? I don't
want to use the replication strategy and I'm not ready to set up a
client-server strategy based upon SQL Server. Given 3 or 4 users and
low volume of transactions, will a single .mdb file work resonably
well? Thanks

Considering the fact that Access even has settings for locks and that there is a
Newsgroup named "microsoft.public.access.multiuser" there should be little doubt
that Access supports concurrent users.

You might have seen conflicting info about "how many" or "how well" Access/Jet
handles concurrent users, but anyone who told you it wasn't possible at all is
really out of the loop.

 

[Tony Toews]

I'm getting conflicting info about multi-user, concurrent access to a .mdb
database. Assuming I'm using a shared folder on a network server, can other
Access users on that network engage in updating activities according to the
locking strategy I've chosen? I don't want to use the replication strategy
and I'm not ready to set up a client-server strategy based upon SQL Server.
Given 3 or 4 users and low volume of transactions, will a single .mdb file
work resonably well?

One client is running 25 users in all day long. With about 10 of them
doing lots of data entry and updates.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Dave Harney]

Thanks for all the comments - really appreciate it!