"unrecognised database format"

connexion

Registered User.
Local time
Today, 22:15
Joined
Jul 30, 2003
Messages
72
I've seen plenty of threads suggesting possible causes for this problem and numerous suggestions for possible fixes.

My Access 2000 database is split in to a back end of around 70-80Mb and 5 users on the front side. No one's exiting stupidly and nothing out of the ordinary is happening, but...here's the best bit...it breaks during the early afternoon each day!! I get all users to exit and then copy and compact using a compactor utility from peter's software.

I also do a compact each night just to keep it neat and tidy, so compacting isn't exactly being overlooked.

I've had the db for around 6 years and archive data out (carefully) every so often to keep it as small as possible. Through history it has been fine and i cope with running it with no major issues. One thing i have never come across though is any kind of event logging gadget that could be used to record what access was doing when it messed up, does anyone know of anything like this that can pinpoint potential problems?

Vince

PS - I'm about to upgrade to Access 2003, is it any more robust?
Plus, are there any differences that might stop my current code in it's tracks?
 
Have you checked with your network admin(s) to see if there is any kind of network interruption going on about that time? That is one big cause of corruption and especially if the users are all opening the same database fron-end file. If that is the case, the users should really have their own copy of the front end and if they do, I'll bet you that you won't have near the problems that you are experiencing now.
 
Hello Bob,

There's nothing special happening on the network at that time and the users do all have their own copy of the front end.

If only it were that simple! lol
 
Next, what I would do, if I were you (because I don't know of any other tools available) is to implement an error logging within the database AND, if you aren't doing it already log users as they log in and out. Then, if you can get the time when the problem has happened, look to see who was in it, and if no errors logged, go to their machine and look at their machine's event log.
 
You're not daft are you Bob!

I've already got an audit table and can easily append records to it to record in/out activity.

Still... if seomeone terminates the application "unexpectedly" i won't get a record created and i'll be seeing who was in but not who fell out! (and they're sure to deny it!) LOL

What the heck for 10 minutes code changing at least it will tell me something!

Vince
 
Troubleshooting can be a royal pain in the ... and sometimes just downright horrible. I know there's not a lot to go on, so good luck and hopefully someone else has figured out something else that might track it down and can post it here.
 

Users who are viewing this thread

Back
Top Bottom