Yikes! Error in table....

marydoyle9

Crckrs9
Local time
Today, 16:50
Joined
Mar 5, 2003
Messages
17
Can someone help me please... have a database, users enter/update the data using forms. I had two users that tried to update at the same time. Two of the fields show "#Error" in them and when you try to access this recird you get a message "The
Microsoft Jet database engine stopped because you and another user are attempting to change the same data at the same time".

How do I fix this? I tried to go into the table and that doesn't work. Tried an update query and that doesn't work either. Oh - one more thing... after a few tries, I get a message saying Access encounters errors and a log is being written and Access is shutting down. Then *poof* - it closes. Where the heck is this log file?

I am not an Access programmer so gotta keep this simple...;)

Thanks!
Mary

If you need, I can send a printscreen of the errors.... let me knwo. Thx.
 
First try to repair or compact/repair depending on your Access version. If that doesn't fix the problem, you are going to have to isolate the bad record. Create a new table. Copy all the rows prior to the bad record, add the bad record manually, copy all the remaining rows.
 
Hi Pat,

Do you have any ideas about how to isolate the bad record? I have a back-end database that may be corrupt but I'm not sure. I tried using DTS in SQL Server thinking that SQL Server would refuse to import a bad record. I finally figured out that the records that DTS had errors with were records with date fields with data out of the range allowed by SQL Server. Access is too tolarant when it comes to certain things. As far as you know, is DTS a useful tool for isolating corrupt records?

Thanks,

Mike
 
I have never used DTS. The corrupted tables that I've had to fix have been Access tables. If the table is too large to identify the record by manual inspection, use a binary search to find it. Create a query that copies and appends the first half of the rows and then do the same for the second half. Keep breaking each set of records in half until you find the bad one. Use the Top 50% predicate to help you with the halving process.
 

Users who are viewing this thread

Back
Top Bottom