F
frank
Hi,
I have an Access 97 MDB which contains a corrupt table with over 200,000
records in it. The corruption isn't really that bad from the point-of-view
that you can retrieve data from it, query it, etc...
However, whenever I try to sort the problem by putting the data elsewhere it
fails with the error "record is deleted", or one that says "The Microsoft
Jet database engine stopped the process because you and another user are
attempting to change the data at the same time". This happens on a copy of
the MDB file which only I am accessing.
To recover the data I have tried appending all records into another access
table, appending them into a remote MS SQL Server table, exporting them to a
text file, importing the table from the MDB into a new one, repairing the
database, compacting the database, etc... all the usual tricks but all fail
with the previously mentioned error messages.
Because there is over 200,000 records it's very hard to track down the
corrupt records but I think it might be errors within some memo fields.
Anyway, this data is fairly important (it wasn't me that set up the
database) and I'm concerned that the corruption will worsen and I may lose
the data. I really want to get the data on SQL Server ASAP, but can't.
Any advice or suggestions?
I have an Access 97 MDB which contains a corrupt table with over 200,000
records in it. The corruption isn't really that bad from the point-of-view
that you can retrieve data from it, query it, etc...
However, whenever I try to sort the problem by putting the data elsewhere it
fails with the error "record is deleted", or one that says "The Microsoft
Jet database engine stopped the process because you and another user are
attempting to change the data at the same time". This happens on a copy of
the MDB file which only I am accessing.
To recover the data I have tried appending all records into another access
table, appending them into a remote MS SQL Server table, exporting them to a
text file, importing the table from the MDB into a new one, repairing the
database, compacting the database, etc... all the usual tricks but all fail
with the previously mentioned error messages.
Because there is over 200,000 records it's very hard to track down the
corrupt records but I think it might be errors within some memo fields.
Anyway, this data is fairly important (it wasn't me that set up the
database) and I'm concerned that the corruption will worsen and I may lose
the data. I really want to get the data on SQL Server ASAP, but can't.
Any advice or suggestions?