database super bloat?

[Dave]

i have an access app that has a split database. i develop it on windows xp
with office xp and distribute with the runtime using the packaging wizard...
all well so far. most of the users testing it now are doing just fine. the
backend mdb file is normally about 1mb. to do regular backups of the data i
recently put in a way to compact the backend file and then copy it to a
floppy. on one testers machine this backup file grew from 1mb to 54mb!
anyone ever seen this?? any ideas??

 

[Joseph Meehan]

i have an access app that has a split database. i develop it on
windows xp with office xp and distribute with the runtime using the
packaging wizard... all well so far. most of the users testing it now
are doing just fine. the backend mdb file is normally about 1mb. to
do regular backups of the data i recently put in a way to compact the
backend file and then copy it to a floppy. on one testers machine
this backup file grew from 1mb to 54mb! anyone ever seen this?? any
ideas??

Have you tried to have them do a manual repair and compact?

 

[Dave]

Have you tried to have them do a manual repair and compact?

can't do that on a runtime installation.

 

[Joseph Meehan]

can't do that on a runtime installation.

I was afraid of that. I have never worked in an environment using the
runtime system.

 

[Dave]

I was afraid of that. I have never worked in an environment using the
runtime system.

i've got the call to compact it in the code after closing the backend, that
seems to work ok except in this one case where it got huge instead. i seem
to remember something long ago and far away about something that can do
this, but can't find any reference to it now.