[AccessD] Hosed back end

Rocky Smolin rockysmolin at bchacc.com
Mon Dec 14 12:34:59 CST 2009


I forwarded the link to the client.  Looks like a good option if their
restore doesn't work out.

Thanks

Rocky


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Schapel
Sent: Monday, December 14, 2009 10:21 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Hosed back end

Rocky,

Yes, I would try JetComp as suggested by Rusty.

If that doesn't do the trick, I can recommend the service provided by Wayne
Phillips at http://www.everythingaccess.com/accessdatabaserepair.htm

Regards
Steve


--------------------------------------------------
From: "Rocky Smolin" <rockysmolin at bchacc.com>
Sent: Tuesday, December 15, 2009 6:12 AM
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Subject: [AccessD] Hosed back end

> Dear List:
>
> Client has a back end which I think was corrupted by a remote user 
> dropping out at an inopportune moment.  But when I try to open this 
> database I get the message that the database is corrupted would I like 
> Access to try to fix it. I say Yes and the hourglass shows but nothing 
> happens - I don't even see the db1.mdb which gets created during a 
> compact - don't know if that is supposed to happen in a repair.
>
> Anyway, after 5 minutes I terminate it as I don't think it's going to 
> complete successfully. Decompile doesn't work - I get the same dialog 
> box asking if I want Access to repair it. The mdb is only 27MB so I 
> don't think it should take more than a couple minutes to repair.  I 
> could put it on a second machine and let it run for an hour - see if 
> anything happens.
> Could
> it take more than a few minutes to repair a 27MB mdb?
>
> I tried importing the tables into a clean mdb but I can't open the 
> hosed database to see the tables.
>
> They can restore from Wednesday's backup so they're not dead in the water.
> But is there any other alternative to repairing or recovering the data 
> from this mdb?
 

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list