Slimming down an application

  • Thread starter Thread starter Laurel
  • Start date Start date
L

Laurel

I have an application that behaves differently on different computers. It
has suddenly begun to behave irrationally on 3 out of 5 computers. The
problems are in formst that haven't been edited, but which are large and
complex. After checking out OP Sys and Access release levels, my best guess
is that the problems happen on the computers with the fewest resources, so I
undertook to try to slim down my app. But I find that after deleting unused
functions in the Modules, the size of the app not only doesn't get smaller,
it gets larger by 4 or 8 kb. (??). Also, the memory used by the various
options is going up, not down. I haven't yet checked my efforts on any of
the problem computers, but could someone explain to me why the size of the
..mdb file doesn't get smaller when I remove code and forms? I do a
Compress/Repair every time.

I'll write a separate post about the specific problems that have cropped up,
to see if someone has a more information/better theories. Or just other
theories.
 
You haven't mentioned which version of Access. In Access 2003 (and probably
2002, I can't remember) compacting the database fails to recover all lost
space and so the file increases in size over time even when regularly
compacted. You need to periodically create a new mdb file and import
everything from the "old" one.
 
Back
Top