I don't usually, but... 10035
I don't usually, but... 10036
Then you obviously haven't "used it very hard". And before you regurgitate the word 'moderate', I mean anything more than: 10 PRINT "HELLO WORLD" 20...
For moderate record counts and concurrent users, Access is very stable. I've used it heavily for nearly 10 years, and rarely see data issues.
If their Access systems (version 97 and later) are unstable, by far the most likely problem is the users are inexperienced and built bad table and database and-or form designs. Tables without proper or any primary keys are a common cause of problems. A table with no primary key, that also contains memo fields, is an invitation to disaster. It's also important that the fields be sized correctly according to the type and amount of data being stored.
Flaky network connections can sometimes corrupt Access tables, too, but this is rare in my experience.
If multiple users are opening the same .mdb from a shared drive, and accessing data from forms in that .mdb, they might have problems - that's a big no no. In that situation:
I don't usually, but... 10037
Dave.J Eggleston But I have, and it rarely lets me down. Is that all you can do? No wonder you think so little of Access' capabilities - you have none yourself. I, on the other...
* put the data tables in their own "back-end" .mdb file * leave the back-end database in place on the shared drive * create a separate front-end .mdb and put the presentation objects (forms, reports, queries) in it, and create table links to the back-end tables * give each user a copy of the front-end .mdb to run on their own system