Hello all,
This is going to be a rather lengthy "question".
I have an Access 2k database, separated front end/back end. Front end copies are on about 30 workstations and used frequently during the work day. The backend has a table called CLIENTS with approximately 6000 client records. Changes to data in the table are made via a frontend db Form which has CLIENTS as its record source.
During the past week, approximately 6 records have become corrupted in this table. The table itself can still be opened and closed. In most cases, data can be updated without a problem.
But at least once a day, a user will be updating a record, and all fields associated with that record become corrupted. This may happen when the user is actually entering data, or may happen if she has entered data and then left the record (form)open. There has typically been no warning or error message.
I've opened the backend db and found these corrupted records in the CLIENTS table. They are obviously corrupted. When I try to delete them I get the error message about "search key was not found". If I copy the backend database onto my local hard drive, I've had pretty good sucess deleting these corrupt records.
I did a lot of searching for answers, including Google groups and the MS Knowledge base. So far I've tried the following:
First, I uddated the msjet40.dll file on all computers
Next, I used a MakeTable query, to deposit all the good records into a new table, deleted the original CLIENTS table, and renamed the new one CLIENTS.
I then created a new blank database, and imported all the objects from the old database, renamed the new database to the old name, deleted the old database, and copied the new one back onto the server.
Everything seemed fine for a day. Then yesterday I opened the database and received an error message that the backend database was in an unrecognizable format or had been damaged. When given the option to try and repair it, I clicked "Yes". Compact/repair started. Abouthalf way through the process, Access stopped responding entirely.
I then tried using Jetcomp.exe to repair. That also hung up about 1/2 way through.
Unsure what else to do, I restored the backup copy of the database that was saved last night on the server.
This morning everything was working fine until I was making changes in record. When I clicked to close the form, I got a "write conflict" message that another user had made changes in the records since I opened it- did I want to save changes, copy to clipboard, or not save changes. If I clicked NO, the form closed fine. I could reopen and access the record. If I clicked YES, the record became corrupted. I purposely chose this particular record because it was a very old one that I knew noone else would be working on.
So the bottom line is that I still have a sick database. Our agency depends on this database daily to track referrals, evaluation, and treatment for special needs children. It would be disastrous to lose it, but I am absolutley out of ideas as to what I should do next. By the way, I do not have a Memo field in this table.
If you have any suggestions beyond what I've tried, please respond.
Lee
This is going to be a rather lengthy "question".
I have an Access 2k database, separated front end/back end. Front end copies are on about 30 workstations and used frequently during the work day. The backend has a table called CLIENTS with approximately 6000 client records. Changes to data in the table are made via a frontend db Form which has CLIENTS as its record source.
During the past week, approximately 6 records have become corrupted in this table. The table itself can still be opened and closed. In most cases, data can be updated without a problem.
But at least once a day, a user will be updating a record, and all fields associated with that record become corrupted. This may happen when the user is actually entering data, or may happen if she has entered data and then left the record (form)open. There has typically been no warning or error message.
I've opened the backend db and found these corrupted records in the CLIENTS table. They are obviously corrupted. When I try to delete them I get the error message about "search key was not found". If I copy the backend database onto my local hard drive, I've had pretty good sucess deleting these corrupt records.
I did a lot of searching for answers, including Google groups and the MS Knowledge base. So far I've tried the following:
First, I uddated the msjet40.dll file on all computers
Next, I used a MakeTable query, to deposit all the good records into a new table, deleted the original CLIENTS table, and renamed the new one CLIENTS.
I then created a new blank database, and imported all the objects from the old database, renamed the new database to the old name, deleted the old database, and copied the new one back onto the server.
Everything seemed fine for a day. Then yesterday I opened the database and received an error message that the backend database was in an unrecognizable format or had been damaged. When given the option to try and repair it, I clicked "Yes". Compact/repair started. Abouthalf way through the process, Access stopped responding entirely.
I then tried using Jetcomp.exe to repair. That also hung up about 1/2 way through.
Unsure what else to do, I restored the backup copy of the database that was saved last night on the server.
This morning everything was working fine until I was making changes in record. When I clicked to close the form, I got a "write conflict" message that another user had made changes in the records since I opened it- did I want to save changes, copy to clipboard, or not save changes. If I clicked NO, the form closed fine. I could reopen and access the record. If I clicked YES, the record became corrupted. I purposely chose this particular record because it was a very old one that I knew noone else would be working on.
So the bottom line is that I still have a sick database. Our agency depends on this database daily to track referrals, evaluation, and treatment for special needs children. It would be disastrous to lose it, but I am absolutley out of ideas as to what I should do next. By the way, I do not have a Memo field in this table.
If you have any suggestions beyond what I've tried, please respond.
Lee