Bad entries - is there an error log?

j0se

Registered User.
Local time
Today, 16:20
Joined
Jan 15, 2003
Messages
57
I have a small access db in a network which has started to crap out far too often lately. The main table records job entries and inserts a date stamp. Every now and then, an entry has a ridicuous ID (auto inc field) and/or a bad date stamp and i can't delete the record (instead i have to output everything to ecel as best i can, reimport it to a table and reset al the fields..)

i don't know what the problem is but i'm wondering if access writest to a log file somewhere (that might help) or if there is a way to make it do this?

cheers
jg
 
1. There is a place to look. It is called the Application Event log, which is kept by Windows, not specifically by Access. You need to be a Sys Admin or otherwise have special rights on the machine in question to see this file.

2. Part of the problem is that if the DB is on a shared drive, you might also be looking for NETWORK glitches. I.e. Access didn't die, it was just given crap by a dying network. That would be the SYSTEM log, not the APP log.

3. Look for any case where you can show by observation or other techniques that any of your users is disconnecting from the database by shutting off the machine. Normally the system shouldn't allow you do to a shutdown until your disk buffers are flushed, but if Access hasn't gotten a full buffer yet, there might be no active disk buffers registered yet. If you find someone turning off their machine - particularly if they do it with the power switch - or worse, the switch on the external power supply - slap them. When you are done, slap them once or twice for me, just on general principles. Wear sand-paper gloves when you do.
 
cool

thanks for that

i wil slap them first... THEN ask questions
:)
 
Also, have you tried compacting and repairing? Sometimes doing this will allow you delete the bad records, without having to export to Excel and re-import.
 

Users who are viewing this thread

Back
Top Bottom