Web Images Videos Maps News Groups Gmail more »
Recently Visited Groups | Help | Sign in
Google Groups Home
microsoft.public.access
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Why does system crash when Compact and Repair Database is used
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
kpuni...@yahoo.com  
View profile  
 More options Feb 17 2006, 5:15 am
Newsgroups: microsoft.public.access
From: kpuni...@yahoo.com
Date: 16 Feb 2006 10:15:32 -0800
Local: Fri, Feb 17 2006 5:15 am
Subject: Re: Why does system crash when Compact and Repair Database is used
Reply to author | Forward | Print | View thread | Show original | Report this message | Find messages by this author
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


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google