MSAccess MDB corruption

Corruption can happen for any number of reasons and is VERY difficult to fully diagnose.

Is your code compiled?  Have you tried a compact and repair?

It was written by an outside vendor.  The code is compiled.  The file repairs when you open it.

"The Citrix servers reboot nightly – some end-users are bad about logging out correctly and leaving sessions idle."

This is DEFINITELY an issue.  This COULD BE the cause.  As an Access Developer, I would build something in that requires users to be kicked out prior to rebooting sessions.  If there are too many broken sessions, this could do it.

Again, there are simply too many variables to answer this simply.

Network appears to be solid.
It is a VB6 app running as an Access app.
The database is not split so Citrix users are sharing the same db.

Could it be oplocks?

http://msdn.microsoft.com/en-us/library/windows/desktop/aa365433(v=vs.85).aspx

Corruption can happen for any number of reasons and is VERY difficult to fully diagnose.

I suppose it is possible.  I am hesitant to say it ISN'T something.  I think that it is most likely the user not canceling and the server rebooting.  If I had an Access database on my computer and kept Killing processes while I was in it, then the likelihood of corruption would escalate.  If you compound that on the number of users that you have it isn't good.

The hardest thing to say about corruption is that we never know what the proverbial straw that broke the camel's back was.  We don't know "how close it is" to corruption.  Lastly, it is, unless there is a specific thing that is triggering it always (I have seen it happen with a lack of compiling the code and compacting and repairing), it is hard to duplicate on command.

The answer to your question is simple, but hard to hear and hard to give.  I don't think anyone can definitively answer it without a doubt.  The best is speculation upon years of experience.

I would add a pre-reboot script that looks for disconnected sessions and logs them out.  (If you let the timers do it, they perform a reset, and not a logout).  If the users not logging out is the problem, then this should help.

Coralon