Yes ... When I choose this database for import it give the error and
doesn't show the listing of objects.
Your database may be corrupted beyond repair. You might check with one of
the Data Recovery services mentioned on the following website to see if they
can help you out.
http://www.granite.ab.ca/access/corruptmdbs.htm

Signature
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html
> Yes ... When I choose this database for import it give the error and
> doesn't show the listing of objects.
wschanks@gmail.com - 22 Mar 2006 19:57 GMT
That's what I had feared, I just wanted to make sure.
Thanks for your help. We have the database being restored, and have
only lost 1 day's work.
Maybe it's time to move this to a SQL Server backend.
Lynn Trapp - 22 Mar 2006 21:06 GMT
You're welcome. Best wishes with it.

Signature
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html
> That's what I had feared, I just wanted to make sure.
>
> Thanks for your help. We have the database being restored, and have
> only lost 1 day's work.
>
> Maybe it's time to move this to a SQL Server backend.
This memory is several years old and very foggy, so take that under
advisement:
Make sure you try to "fix" the back end first.
I remember a case where the corruption was in the backend (easily fixed with
a compact) but there was no way to get into the frontend (even to import
objects) until that was dealt with. Once the backend problem was fixed, all
problems were fixed (i.e., the frontend no longer had any issues).
HTH,

Signature
George Nicholson
Remove 'Junk' from return address.
> Yes ... When I choose this database for import it give the error and
> doesn't show the listing of objects.