|
|
microsoft.public.access |
Thanks for your reply. > Anyway, make sure you're making a backup copy of your database before you > hth, > Nick > "R J Kershaw" wrote: > > In Access 2003 the command 'Compact and Repair Database' causes the system
I have already done the backup bit (sound advice anyway), but there is no
apparent corruption and the links are still there.
Will try the procedure with a completely unlinked DB.
Unfortunately there is no other machine to test this on so I hope it doesn't
come to the need for application or operating s/w reinstallation - I have too
much else going on!
Best regards,
Bob K
"Tatakau" wrote:
> I sometimes come across the problem where compacting and repairing a database
> will actually corrupt my database, or invalidate the links to my tables.
> Mostly I think this is due to the complexity of the front-end I am working
> on, or the number of different databases I'm linked to, or just whatever else.
> try to compact and repair. You said yours is crashing when you try doing
> that, so test it on a simple database to see if it'll work on something
> small. If that doesn't work, try converting to an older version of Access
> first (Acces 2000 or in an extreme circumstance, Access 97). Failing that,
> try compacting on a different machine. If it's still crashing, then it's
> probably an Access problem, and you'll want to re-install Office on your
> machine. If it's not working by that point, I would personally re-install
> the OS (because it might be a library or extension problem), but that's just
> me. I'm odd like that. :-p
> > (Windows XP Professional) to crash, with an error message saying it has to
> > close.
> > Why is this and what do I have to do to stop it?