Limit of Access

[kelvin H via AccessMonster.com]

How many records can Access handle without obviously slow ?
will Access be affected by concurrency of too much users edit the database ?

Thx ~

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200511/1

[Allen Browne]

If you anticipate millions of records or many scores of users, it would be a
good idea to start with another database engine.

If you already have an Access database with millions of records and 100
users, it may still be possible to have it work well.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"kelvin H via AccessMonster.com" <u13193@uwe> wrote in message
news:5806d7fec8924@uwe...

How many records can Access handle without obviously slow ?
will Access be affected by concurrency of too much users edit the database
?

[Larry Linson]

"kelvin H via AccessMonster.com" <u13193@uwe> wrote

How many records can Access handle without obviously slow?
Many factors affect performance, including the software, hardware, and
network environments and the requirements, design, and implementation. If
all factors are near-optimum, people report satisfactory performance with
100+ users in an all-Access-and-Jet environment. We presume all factors are
just about as distant from optimum as they can be in the case of a few
people who report "Access falls over with 4 users". In fact, I know that if
you go out of your way to make it so, you can create a database that will
not even support a single user.

Look for my presentation on Access in a Multiuser Environment in the
"downloads" area of http://appdevissues.tripod.com for an introductory
overview of "multiuser". For the very best collection of information and
links that I have found on performance and corruption-avoidance see MVP Tony
Toews' site, http://www.granite.ab.ca/accsmstr.htm.
will Access be affected by concurrency of too much users edit the

database?

Yes, it can. The question is "how many is TOO many". For which, see above
and the above links.

Larry Linson
Microsoft Access MVP