Serious Bloating issue, factor of 100

[Paul]

Hi,
I recently updated my application from ACC2002 to ACC2007 and made a visit
to a few of my customer sites today and noticed that my front-end accde file
has grown from approximately 20M to over 2GB. I couldn't believe my eyes.
ACC2002 bloated, but never at this rate, maybe a factor of 2 or 3. This
situation has me frightened, is this a time bomb waiting to got off. The file
seems to have reached its maximum size? It does not seem to affect
preformance, but it is sure wasting disk space. It is a little embarrassing
when I need to tell potential clients that my 20 MB application needs 2GB of
disk space.
Why is this happening?
Why only since ACC2007?
What can I do to prevent this?
What will happen when the file reaches its max size?
Can it affect performance?

Thank you,
Paul

 

[Jeff Boyce]

Paul

Give this a try...

An .accde is not the original, but a psuedo-executable. Go back to the
original (.mdb for A02; .accdb for A07), make backup copies.

Open Access 2007, then open the .mdb file from within Acces 2007, and Save
As an Access 2007 database. Run Compact and Repair on this converted
version. How large is it now?

Create your .accde from the version you've run Compact & Repair on.

What size it that now?

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Tony Toews [MVP]]

I recently updated my application from ACC2002 to ACC2007 and made a visit
to a few of my customer sites today and noticed that my front-end accde file
has grown from approximately 20M to over 2GB. I couldn't believe my eyes.
ACC2002 bloated, but never at this rate, maybe a factor of 2 or 3. This
situation has me frightened, is this a time bomb waiting to got off. The file
seems to have reached its maximum size? It does not seem to affect
preformance, but it is sure wasting disk space. It is a little embarrassing
when I need to tell potential clients that my 20 MB application needs 2GB of
disk space.

Do you have A2007 SP1 installed?

Why is this happening?
Why only since ACC2007?
What can I do to prevent this?

No idea. We've had occasional similar comments such as this but
nothing quite so extreme.

What will happen when the file reaches its max size?

2 Gb is the maximum size.

Also consider importing into a new ACCDB file.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Paul]

Thank you for responding Tony!

Do you have A2007 SP1 installed?

Yes, on my development computer. I don't see this bloating on my machine
since I am constantly compacting.
This is occurring on my customers' computers with runtime version
12.0.6237.1003 which appears to be the most recent.

No idea. We've had occasional similar comments such as this but
nothing quite so extreme.


2 Gb is the maximum size.

Are you saying that nothing will happen?
If that's the case then why can't Access limit it's own size? If it stops
growing at 2 GB, then why can't it stop at some arbitrary lower number?

Also consider importing into a new ACCDB file.

I do this on a regular basis.

Is Microsoft looking into this issue?

 

[Paul]

Thanks Jeff!

I am not sure I am following. It sounds like you're suggesting that I go
back to my 2002 file and reconvert to 2007. That's just not practical, or
even possible, at this point. I have invested about 2 months worth of changes
to get from 2002 to 2007.

 

[news.microsoft.com]

Are you saying that nothing will happen?
If that's the case then why can't Access limit it's own size? If it stops
growing at 2 GB, then why can't it stop at some arbitrary lower number?

The 2 GB limit of the database has been reached. If it gets any bigger, it
will probably corrupt. I would import everything into a clean empty
database, compact and compile. I'd then build a way for your users to
compact, and train them to do nit regularly. Alternatively, you can put a
clean, connected front-end on the server and have users download a new one
at regular intervals.

 

[Paul]

Thank you for the workarounds Arvin, but I am more interested in knowing why
this problem is not being addressed, I am baffled by this. This is a
frent-end file deployed on many computers, it is not even carrying any data.
This was not an issue prior to ACC2007. Surely what was broken can be fixed?
How can anyone justify letting a file grow until it surpasses its maximum
allowed size and corrupt data? If this is not a showstopper issue, then what
is?

Please someone at Microsoft, step up and fix this.
Paul

 

[Paul]

Update <<<

I happened to have my file explorer opened while my bloating access
application was running and noticed that the file size increased in front of
my eyes, but there was nothing going on in the application. I have a timer
running every 10 seconds and this coincided with the rate at which the file
was growing. Naturally I suspected something in my timer routine. To debug, I
stubbed out the OnTimer code;

Private Sub Form_Timer() 'temporary
End Sub

but the growth continues. It grows by about 45,000 bytes every tick. Can
anyone help with this?

Thanks
Paul

 

[Arvin Meyer [MVP]]

Hi Paul,

Now that we have something to go on, I'll try to escalate this to Microsoft.
Get in contact with me privately at the email address listed at the website
in my sig below.