Message from discussion Why does system crash when Compact and Repair Database is used

Thread-Topic: Why does system crash when Compact and Repair Database is used
thread-index: AcYgTqh2YC2pB/YIQPaGpW6pSxhx+Q==
X-WBNR-Posting-Host: 195.93.21.73
From: "=?Utf-8?B?UiBKIEtlcnNoYXc=?=" <RJKers...@discussions.microsoft.com>
References:  <B61B1879-42EA-4BDD-9514-DA1B2ED18A0D@microsoft.com> <3B0315A8-90D9-496E-A473-1B4CFE688724@microsoft.com> <147918CA-D93C-42F9-9D66-A5B1B158E31B@microsoft.com> <#alYdN5HGHA.3056@TK2MSFTNGP09.phx.gbl>
Subject: Re: Why does system crash when Compact and Repair Database is used
Date: Mon, 23 Jan 2006 10:56:03 -0800
Lines: 73
Message-ID: <A766AFE0-6E9C-4DAA-A016-69790DDACE4A@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.access
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: g2news1.google.com!news1.google.com!news4.google.com!news2.volia.net!newsfeed.gamma.ru!Gamma.RU!nntp.abs.net!ash.uu.net!news.mcleodusa.net!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl

Many thanks for your kind assistance.
Bob K

"G. Vaught" wrote:

> Temporarily disable your McAfee; disconnect from the Internet if you want to 
> feel safe if you have a 'always on' connection. McAfee can interfere with 
> Microsoft from time to time.
> Also make sure the location of the database has enough hard drive space, 
> which I tend to believe that is okay, since your machine is new.
> 
> The other option you have is create a new database and import tables first, 
> then queries, then compact that part. Continue importing the remainder of 
> your database. Do forms last, as sometimes a form gets corrupted and it 
> prevents the import of other items. If you do have a corrupted form, then 
> you may have to just recreate that form in the new database. Once everything 
> is imported, make a backup copy and then compact that new database.
> 
> 
> "R J Kershaw" <RJKers...@discussions.microsoft.com> wrote in message 
> news:147918CA-D93C-42F9-9D66-A5B1B158E31B@microsoft.com...
> > Thanks for your reply.
> > 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.
> >>
> >> Anyway, make sure you're making a backup copy of your database before you
> >> 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
> >>
> >> hth,
> >>
> >> Nick
> >>
> >> "R J Kershaw" wrote:
> >>
> >> > In Access 2003 the command 'Compact and Repair Database' causes the 
> >> > system
> >> > (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? 
> 
> 
>