I know I'm supposed to split the database, but...

[Guest]

Ok, I've got a split database on a LAN. Each user is running from their
desktop, but my problem is that every day, the backend is getting corrupted.
Will this stop if I just go to a database that is not split, all running from
the network?

Thanks,

Nathan

 

[Joseph Meehan]

Ok, I've got a split database on a LAN. Each user is running from
their desktop, but my problem is that every day, the backend is
getting corrupted. Will this stop if I just go to a database that is
not split, all running from the network?

99% of the time when this happens you have a poor LAN connection or more
likely someone is just turning their computer off without first shutting
down Access.

My users all learned to shut down Access properly before shutting down
their computer. If you can't teach them to do it right, then you might try
a system to kick them off after so long in inactivity. That might help, or
might not.

 

[Rick Brandt]

Ok, I've got a split database on a LAN. Each user is running from their
desktop, but my problem is that every day, the backend is getting corrupted.
Will this stop if I just go to a database that is not split, all running from
the network?

In all likelihood the problem would get much worse. This is one of the main
reasons to split in the first place. Splitting does not however make corruption
impossible if you have bad hardware or user practices that make corruption
likely to occur. It just makes the environment more optimal.

Access is a "canary in a coal mine" as far as network hardware is concerned. If
someone has a flaky NIC, hub, or switch on their network a shared Access app
will be the first thing to let you know about it. I would suggest running some
diagnostic software on the LAN and on all PCs that use your app.

 

[Guest]

Thanks to both of you for the post. I've talked to the ITM dept here, and
they are going to do some monitoring. I think I have it narrowed down to a
specific user that does exit correctly. So maybe they will find something in
that pc or switch.


Thanks

Nathan

 

[Guest]

I like Rick's "canary in a coal mine" analogy. It's very, very true.

Suggest to your IT people to run a sniffer on the network. Could be some
corrupt packets floating around and these might even come from a computer not
using the database!

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp