FE Corruption

[TKnight]

Hi,

I have a split FE/BE system running on a network and I am having a few issues with the FE's corrupting...

Occasionally a user will call up saying they can't get in and when I go, I get the "microsoft jet database engine could not find object MsysDB" error message which basically means corruption right?

It's not difficult to fix because I can just get a fresh copy of the FE and it works fine but it's happened 3 or 4 times now so I want to try and track down the source of the problem if possible.

The wierd thing is that i'm not pushing Access too hard (unlike normal). 20 odd users (probably only 4 or 5 simultaneous), and the BE is only 200mb. The only thing different to my normal DBs is that I am getting getting data from a web service every 5 mins between 06:00 and 22:00. That data goes into a separate BE which links into the FE. Could it be that constant activity which is causing the FE corruption?

If it helps, no users have reported the DB crashing, it closes fine when they last used it but when they next log on the message appears?

I saw an old post by GHudson about the Jet Compact & Repair but I didn't try it because I can fix the problem so easily - i'm trying to stop it happening if possible.

Any thoughts from you guys would me much appreciated.

Cheers,

Tom

 

[Rabbie]

Does each user have their own copy of the FE on their own PC?

 

[gemma-the-husky]

i have complex login forms etc, that occasionally produces this error in one user or another - i just copy a new version of the front end, and all is well

 

[TKnight]

Rabbie: Yeah each user has a copy of the FE.

Gemma: If it only happens once in a while it's not so bad. I guess the error is generated at runtime so I could probably trap it and automatically replace the corrupt FE. I'm using an auto-update function to roll out new versions anyway so this shouldn't be too hard.

Thanks for your input!

Tom

 

[Rabbie]

You could try setting the FE up to do a Compact and Repair on close.