Hi,

We are considering to use the Jet 3.0 format in our applications, but we
would like them to be multi-user applications. The number of users would be
less than 10. In the past we have had a lot of corrupted database problems
with Jet 2.x applications that were used by up to 5 or 6 users
concurrently.

Does anyone know if Jet 3.0 has been improved in this respect? In other
words is it more robust in multi-user situations than Jet 2.x? Any pointers
to more information or documentation would be greatly appreciated.

Thanks in advance,

Lambert Wolterbeek Muller,
Davilex Software.

PS. We are aware of the fact that a client/server solution would solve this
problem, but that is not an option at the moment.

Check your hardware, upgrade if necessary. What network are you on; set
file server locks to the maximum since this can be a problem with large
Access queries.
Corruption problems in MS Jet usually occur when PC's experience hardware
problems, or connections to an open database are broken. My agency has
several Access 2.0 databases shared on a Novell Netware 3.12 server, with
users across the state of Texas dialing in via PCanywhere and running
remote sessions, both on a 56kb data circuit, and over standard telephone
lines with 2400 baud modems.
We have one large database that 50 users constantly access, and it has
experienced corruption problems (somtimes 5 times a month, but can go for 6
months without a problem).
Corruption occurs: 1) when dial-in users experience telephone line
difficulty and the connection is broken; 2) when a user's PC hard drive or
memory fails, at which point they end up re-booting. We almost never have
problems on the local area network connections.
Before repair and compact, delete the "LDB" (locking database file) first
since it keeps track of locked records which the software may think are the
only records.
And yes, we are making the transition to client server using MS NT/SQL and
Access 7.0 on an Digital Alpha box.