jwcolby
jwcolby at colbyconsulting.com
Wed May 16 09:21:16 CDT 2007
>Failing that, create a new table with the same layout as the first, then do an append from the corrupted table to the new table. This is a good suggestion. If specific records are corrupted then those will fail to copy. Unfortunately it might simply stop when it encounters the first failure. Another thing to try, if a relationship is established between the parent and child table, delete that relationship, then try to delete the offending parent records. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bryan Carbonnell Sent: Wednesday, May 16, 2007 9:27 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Weird Problem...for me anyhow On 5/16/07, John Clark <John.Clark at niagaracounty.com> wrote: > I have a user who has setup her own DB...good that she has an interest > in Access...bad that she THINKS she is capable of doing this. I have > had to bail her out before, and once again my help has been requested. > OK, so maybe I got a little chip on my shoulder w/this one ;o) <snip> > I am about to tell them, "Here is your recovered database. You will need to re-enter the data you've lost. Sorry!" But I wanted to run it by this list first. > > Any ideas?! Couple of Shots in the dark. How about a Compact & Repair? Failing that, create a new table with the same layout as the first, then do an append from the corrupted table to the new table. -- Bryan Carbonnell - carbonnb at gmail.com Life's journey is not to arrive at the grave safely in a well preserved body, but rather to skid in sideways, totally worn out, shouting "What a great ride!" -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com