Hi, Steve Santus.
1. Does that mean that the data that was in the table is forever lost?
Not necessarily, but I don't want to get your hopes up, because chances are
low that data can be retrieved when the table definition is completely gone.
The table definition can be removed during a compact/repair when the repair
fails, or under normal circumstances when a table is deleted. The data
pages are still intact at first, but Jet does housecleaning, and will very
quickly start reusing those data pages, especially if the database file is
closed after the table definition is removed and then the file reopened.
If the corruption is caught quickly enough and the corrupted table
definition didn't cause Jet to move data to, or write the data at, the wrong
addresses in the data pages, then most, if not all, of the records may be
salvageable. That's why it's critical to make a copy of the file as soon as
corruption is detected and only work with the copy when trying to repair it.
That way, if one method fails, one can always go back to the original and
make another copy to start over with the next attempt using a different
recovery method.
If you haven't caught it quickly enough, then most, if not all, of the data
in those data pages is unsalvageable, because Jet has started overwriting
records in the data pages that once belonged to the lost table definition.
2. Is there a way to restore the table definition and be able to access
the data?
There are commercial tools available that can recover data in the data pages
(that is, if you've caught the corruption problem fast enough), even without
the table definition, but they need a copy of the table structure to
reconstruct the table for you in a brand new database file. If you have a
recent backup with the correct table structure, that will help the tool do
its job.
"The Microsofe Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time."
You'll have to use a recovery tool to retrieve the data. You won't be able
to repair the file with a normal compact/repair. Even JetComp isn't very
successful in these cases, but it's worth a try if you haven't used it on a
copy of the database yet.
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs:
www.DataDevilDog.BlogSpot.com,
www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.