Message from discussion
Why does system crash when Compact and Repair Database is used
Path: g2news1.google.com!postnews.google.com!g14g2000cwa.googlegroups.com!not-for-mail
From: kpuni...@yahoo.com
Newsgroups: microsoft.public.access
Subject: Re: Why does system crash when Compact and Repair Database is used
Date: 16 Feb 2006 10:15:57 -0800
Organization: http://groups.google.com
Lines: 68
Message-ID: <1140113757.524874.145600@g14g2000cwa.googlegroups.com>
References: <B61B1879-42EA-4BDD-9514-DA1B2ED18A0D@microsoft.com>
<eOEJov6HGHA.240@TK2MSFTNGP11.phx.gbl>
<1B4D4A57-6577-4563-8B8B-8AFA338008C8@microsoft.com>
NNTP-Posting-Host: 38.114.132.2
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1140113763 26156 127.0.0.1 (16 Feb 2006 18:16:03 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 16 Feb 2006 18:16:03 +0000 (UTC)
In-Reply-To: <1B4D4A57-6577-4563-8B8B-8AFA338008C8@microsoft.com>
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: g14g2000cwa.googlegroups.com; posting-host=38.114.132.2;
posting-account=Cdio_A0AAABbs6l4Xi1aeNMwUsNxfxFP
This is ABSOLUTELY a bug in Access 2003. It not only happens
consistently when you have had a module window opened, but if you have
designed ANY object.
I have a fairly sophisticated front end application that I have
attempted to bring into a new database to try to eleviate the problem,
but it still happens.
The only thing that you can do is make your changes, then fully exit
the application, then you can come back in and Compact.
I wish that Microsoft would just own up to this and fix it. This never
happened in 2000 or 97.
Also, the application seems to crash alot more now that we have
converted it to Access 2003. Again - it was pretty stable in Access
2000, but our IT Dept. forced us to upgrade, so we did. We have had
more problems between the stupid Outlook security (which - we were
finally able to overcome) and these constant crashes.
I think that I've definitely learned my lesson on "if it ain't broke -
don't fix it" and will fight harder next time against an upgrade until
I see the tru benefits.
Good Luck!
R J Kershaw wrote:
> Thanks for that, Albert.
> I now have a number of things to try along similar themes.
> One observation: there is apparently no corruption or data loss taking place
> and the filesize indicates that at least some compaction is happening.
> The mdb type is 2003, the default for Access2003.
> Best regards,
> Bob K
>
> "Albert D.Kallal" wrote:
>
> > There has been a few posts that suggest that having code windows open can
> > case this..
> >
> > Try he following:
> >
> > exit the application
> >
> > re-enter the application (hold down the shift key if you have any startup
> > forms..or any startup code that runs when the application loads).
> >
> > now try a compact and repair. If this don't work..then I would suggest that
> > you create a new blank database..and import everything into this...can you
> > compact that one?
> >
> > It sounds like you have a improper shutdown or free up..and the mdb files is
> > now damanged....
> >
> > Also, what format of mdb file are you using...(the default is 2000...but
> > give the 2002-2003 format a try).
> >
> >
> > --
> > Albert D. Kallal (Access MVP)
> > Edmonton, Alberta Canada
> > pleaseNOOSpamKal...@msn.com
> > http://www.members.shaw.ca/AlbertKallal
> >
> >
> >
|
