mdb repair

Can anyone recommend software for repairing a 2000 mdb? There are many
choices with a wide range of prices but none lets you look at the actual
repaired db prior to purchace.

My problem child opens okay and seems to be functional but apparently the
user has never compacted it in a couple of years and what should be about
30MB is now almost 400MB. It's just data with no forms, code, etc.

It crashes Access, Jetcomp, and the Windows ODBC Data Source Administrator
when I try to repair it. And it crashes Access when I try to import it into a
new db.

Thanks

What happens when you try to import just one table at a time? You may be able
to find just one table that is the problem. You could then use a make table
query to extract most of the records.

Check for problem memo fields. If you can do a make table excluding the memo
fields then export the new table, there's the problem. If you can further
define which record(s) are the problem, you can extract almost everything
except the bad memo data for the problem records.

Have you tried working on the database using another computer? There might
be something wrong with your PCs Office installtion.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"Jay Vinton" wrote:

Can anyone recommend software for repairing a 2000 mdb? There are many
choices with a wide range of prices but none lets you look at the actual
repaired db prior to purchace.

My problem child opens okay and seems to be functional but apparently the
user has never compacted it in a couple of years and what should be about
30MB is now almost 400MB. It's just data with no forms, code, etc.

It crashes Access, Jetcomp, and the Windows ODBC Data Source Administrator
when I try to repair it. And it crashes Access when I try to import it into a
new db.

Thanks

Thanks for the good tips. This was a customer's db and after a lot of (free)
trial & error, I found enough bad records and general weirdness that I sent
them to a data recovery shop.

A few hundred dollars later, they got the db back but that process lost a
bunch of indexes & relations. We fixed that part and it seems to be okay now.
I wish MSDE had been available when this application was born...

Thanks again