Hello all,
Due to some users experiencing severe front end bloating (Normal compacted
front end .accdr is 27MB's, FE can bloat to 80-90+Mb's in a day), I want to
enable the "Compact on Close" option on the front end, and distribute in a
runtime installation.
I do have my share of update / append queries, and I've always suspected
that they are the main culprit, but it's hard to say. One strategy I tried
was to move the frequently used temp tables that I have from the program
..mde file to a local workspace.mdb file. My hope was that having a workspace
..mdb with all the temp tables I use for updating / appending, that the
bloating would occur in the workspace.mdb, but I don't think this idea has
really helped.
Anyway, back to the Compact on Close question. Problem is, I tested on a
side win xp machine, and the compact on close caused the program runtime to
stop responding upon exiting the program. Has anyone else experienced this?
Thanks!
Andy
P.S. I do realize that, with today's huge hard drives, it's not the space on
the disk that is the issue. To me, having a bloat of 3-4X the normal size is
a performance issue, as a 27MB file would naturally load into memory, and
run, faster than a 90MB file.
Due to some users experiencing severe front end bloating (Normal compacted
front end .accdr is 27MB's, FE can bloat to 80-90+Mb's in a day), I want to
enable the "Compact on Close" option on the front end, and distribute in a
runtime installation.
I do have my share of update / append queries, and I've always suspected
that they are the main culprit, but it's hard to say. One strategy I tried
was to move the frequently used temp tables that I have from the program
..mde file to a local workspace.mdb file. My hope was that having a workspace
..mdb with all the temp tables I use for updating / appending, that the
bloating would occur in the workspace.mdb, but I don't think this idea has
really helped.
Anyway, back to the Compact on Close question. Problem is, I tested on a
side win xp machine, and the compact on close caused the program runtime to
stop responding upon exiting the program. Has anyone else experienced this?
Thanks!
Andy
P.S. I do realize that, with today's huge hard drives, it's not the space on
the disk that is the issue. To me, having a bloat of 3-4X the normal size is
a performance issue, as a 27MB file would naturally load into memory, and
run, faster than a 90MB file.