Yes, there are some things that need to be addressed in that environment --
but there isn't a limit on how many people can open a file. The best
collection of information and links on multiuser issues is at MVP Tony
Toews' site,
http://www.granite.ab.ca/accsmstr.htm.
There are also design differences. A well-designed, good-performance
single-user standalone Access application isn't usually a well-designed,
good-performance mult-user Access application. For example, you don't want
to open a Form using a Table or huge Query as the RecordSource... use a
Where clause referencing an indexed field so you only have to bring the
index across the network to select the records for which you need to bring
the rest of the data across. It's surprising how often you only need one
record (if it exists) or none (if it does not) in a Form.
For a more general overview of Access in a multi-user environment, download
a copy of my presentation on that subject from
http://appdevissues.tripod.com/downloads.htm.
Good luck with your project.
Larry Linson
Microsoft Access MVP
"Almarni" <al**********@u konline.co.uk> wrote in message
news:fe******** *************** ***@posting.goo gle.com...
Designed a database in Access 97 that runs on a 2000 server and is
accessed by users using Windows 2000 client.
Reported that no more than 3 users can use it. There is one database
with the tables and the ability for one person to add/edit etc. A
second database links to the tables in the first one and that is
strictly for viewing. I know concurrency can go far higher so
wondering if there is a problem in windows 2000 server some sort of
setting that only allows so many people to open a file.
Any ideas.
Many Thanks.
