Database corrupt

[Cynthia]

I have a document management system I designed in MS
Access. I could not put the database on the network and
thus had to design the database to fit on each employee's
computer. The problem is anytime someone's computer
crashes and they have the database open, it will corrupt
the database and when someone else trys to open it they
will receive the error message that the database needs to
be repaired.
Is there anything that I can do so that this will not
happen if someone's computer crashes?

 

[Brendan Reynolds]

I'm a bit confused here, Cynthia. If the database was not on the network,
but on each employee's PC, then anything that happened to the database on
one employee's PC would have no effect whatsoever on the separate databases
on other employee's PCs. If a corruption on one PC is causing problems for
users on other PCs, then something *is* being shared across the network.

Could you clarify?

 

[John Vinson]

Is there anything that I can do so that this will not
happen if someone's computer crashes?

Well... no.

That's like asking if there's something you can do so that nobody will
be hurt if the car they are riding in crashes.

Keep backups; If you're passing a database around (on diskette or CD?
sneakernet? EMail? or what?) then give each user a COPY of the
database; if they succeed then their copy becomes the master from
which you make the next copy. If they fail you have the copy to go
back to.