Corrupt database

[Vassago]

I have a split database with a very large BE database. The database is usually always over 100 mb. Every single day for the past week, the database has needed to be repaired. I checked the last two days and everyone has logged out of the database correctly using my Exit Database button.(docmd.quit). What could be causing this to happen EVERY day? What kind of things should I look for? I really need some help on this one. Thanks!

Vassago

 

[Autoeng]

That's wild Vass. My db used almost a year crashed this morning also. I have no clue as what happened either but is wasn't on the data side. It was the security workgroup file that went corrupt. Once I restored my backup everything was okey-dokey.

How often to you compact and repair?

 

[Waltang]

I dont know if this will help or not, but about 4 years ago, the database that I built for our company was having the exact same problem. It was compounded by the fact that it was replicated, and so if we repaired it, it lost its replication. (Jetcomp finally fixed that problem) We had experts come in and examine all the hardware and software, and none of them found any problems. About this time, a cold front came through, and for a week we had no problems. As soon as the temperature went back up, we started having problems again. It turns out that our network hub was in an un-airconditioned Storage room, and was getting hot and disconnecting users to the database causing bad exits. We placed the hub inside of a junction box and air conditioned it, and have not had any problems since.

 

[Vassago]

Thanks for the replies,

That's wild Waltang. You would think the IT "pro" would know better than to place a server in extreme temperatures.

Auto - Because of this problem, I've been compacting and repairing daily before I leave, yet sure enough, the problem exists again the very next morning! I don't know what to do, they are pointing their fingers at me, yet obviously, the problem isn't in the code. I may actually have to check the temperature of that server room Waltang!

without an answer...?

 

[andrewf10]

So it's not just me!!

At least once a day every day for the past 2 weeks my Access 2000 database has been crashing and exactly like you, my exit routine log is showing that the users are doing nothing wrong.
A compact and repair job runs every night on it.

OK my DB isnt split between BE and FE but it is only 19Mb. Up to 2 weeks ago, this was only happening at most once a month, and was always linked to a users PCs crashing. But now is different. I'm getting murdered over this.

 

[MattS]

Ever figure this out??

Has anybody figured out a cause for this yet??

I'm having real problems with this at the moment - exactly the same scenario as above. Split db, with all users exiting the FE correctly, and then for no reason it needs repairing.

I've had this happen 4 or 5 times in one day!! Am about to embark down the 'import it all into a new DB' route, but if anybodys got any clues.....

Thanks,

Matt.

 

[andrewf10]

Matt,

I went and logged this as an issue with Microsoft and this is the reply I got from one of their support people. I did revoke one users access and things improved significantly.

**************************************************

In your case you have indicated that when you open your database you receive the error the following error message:

" A user has exited MS Access without closing, database is corrupt and needs to be repaired. "

It is possible that the problem may be caused by the network.

In order to prove/disprove this, please try running the database locally to see if the problem still persists. If it does not then you know that the problem IS network related. It is likely that in this case the problem is caused by just one machine.
Next you will need to try and identify which machine is causing the problem. To do this you will need to use the database on one machine at a time until you find the one that is causing the problem. The problem could be caused by either the network drivers or maybe the network card itself (in which case the network card would need to be replaced.)