why does the database need repairing when used on a network

[Guest]

when I use Access on a local computer it works fine, but if more users on

network use it after a while the repair database warning pops up, and all
have to close the database and when the first user logs back in the repair
process starts, when it's finished there are some records with only ####
in
the fields which must some in them. I have set the record locking and to
all
and open mode to shared.

Does anyone know why this happens?

Steve

 

[Van T. Dinh]

Corruptions do occur. There are a number of possible causes. One that is
often hard to fix is flaky NICs (Network Interface Cards).

From your post, I guess you have multiple users using the same MDB / MDE
file. This set-up will increase the chance of corruptions. For a
multi-user application, you should (more like must, actually) split the
application into Back-End (data, i.e. Tables only) and Front-End (other
Access objects). The Back-End resides on a share directory that all users
can access. Each user should have a copy of the Front-End on his / her
desktop.

Tony Toews has some Web pages on corruption causes:

http://www.granite.ab.ca/access/corruption/causes.htm

 

[Guest]

I will move the database to and XP computer and split the database.
I will keep all informed of the outcome

Thanks to Van t.Dinh