corruption confusion- any ideas are appreciated

[gsc_81]

I'm running Access 2000 through Citrix, 20 users internationally from 1 db. I'm working through Citrix network issues to split db with separate FE's for each user.
I have sporadic corruption due to this. But this morning I met a new breed of corruption. I preface this with the fact that I run a bat file nightly to do clean up and compact and repair the db. It verifies the db is not in use prior to running.
This morning we were presented with a hosed db.
The log file said updates ran fine.
In my main table the first record was garbage, including the Auto-num field. I found that my Primary key has lost it's index and references had become unchecked.
Correcting these issues got it running but does anyone have any clue what might have triggered this or even where I should start looking? Please help as I am at a loss.
Thanks.

 

[The_Doc_Man]

References became unchecked? You had an interloper, I think. Your security is probably not quite right.

Remember that references are really implemented in each user's registry. The only way I recall to lose a reference from a DB is if the last user in the DB didn't have the right references on their system.

Using the CITRIX solution with multiple FE is going to be a headache. You are going to need a lot of memory in your applications host. If you run out of memory, I could very easily imagine - like, in a heartbeat - that something would be corrupted.

Normally, this isn't something that gets openly discussed, but the more users you run on your machine, the more resources you need. Now you might say, "Well, DUH..." - but trust me, it is one of those "out of sight, out of mind" issues that always seems to elude designers.

You face the issues of memory, file handle limits, and page file limits whenever you start sharing apps via CITRIX. Because if I recall correctly, Access doesn't really "know" that it is being shared other than that there are a lot of windows open on the same machine that point to the same .exe files.

I firmly believe your night batch job ran fine. Your corruption might very well have been something that happened that morning, having to do with overall machine load rather than any failure of the cleanup job.

As a side issue, use Event Viewer to see if you have any event logs for about the time when your auto-compacter runs. Just to be sure that nothing unusual was logged at that time. (You DO have Event Logging turned on, don't you?)

 

[gsc_81]

Thanks for the response. Nothing notable in the Event Logs and according to logins it was the first access of the morning that received the error. As far as an interloper I don't even know how someone could corrupt an Auto Num field while still enabling the table to open. It's just been bizzare.
Do you have any suggestions for handling multiple users through Citrix? Even if I sacrifice drive space and processing power my network response time is horrendous using FE's.
As for my original corruption it still remains a mystery to me.