Is this true?

[redant via AccessMonster.com]

i'm hoping for your sake that this is an internal application? is this
actually going out on the open web? are you envisioning more than a handful
of users? access is fine for personal use or small workgroups, but it's file-
based and not designed for any sort of heavy or 24/7 use. you will have
concurrency issues at high volumes, you'll get invalid data when writes can't
keep up with the read volume. 10 simultaneous users max.

 

[Golfinray]

I use 2003 with way over 1 million records and dozens of users and have no
problems whatsoever.

 

[John W. Vinson]

I use 2003 with way over 1 million records and dozens of users and have no
problems whatsoever.

Over the Internet, Ray? That's surprising if so.

 

[Arvin Meyer [MVP]]

you will have
concurrency issues at high volumes, you'll get invalid data when writes
can't
keep up with the read volume. 10 simultaneous users max.

That's ridiculous. Admittedly Access is not design for continuous high
volumes of data, but it keeps up with read volume anywhere just fine, and
write volume to the tune of millions of records when necessary. 10
concurrent users? Ridiculous. At least twice that many, and I've had 53
concurrent users, some heavy, some (8 to 10) via ASP, and some (6 to 8) via
Terminal Services, writing through 75 open application instances, without
any write conflicts or corruption.

 

[redant via AccessMonster.com]

Thanks!

That's ridiculous. Admittedly Access is not design for continuous high
volumes of data, but it keeps up with read volume anywhere just fine, and
write volume to the tune of millions of records when necessary. 10
concurrent users? Ridiculous. At least twice that many, and I've had 53
concurrent users, some heavy, some (8 to 10) via ASP, and some (6 to 8) via
Terminal Services, writing through 75 open application instances, without
any write conflicts or corruption.