Minimizing front end growth

[Brian]

Does anyone have any tips on minimizing front end growth in fe/be splits? In
specific, I noticed these:

#1: While under development, my db's tend to grow, even with regular compile
& compact/repair. In one example, it had grown to about 12 MB. When I created
a blank DB and imported all the objects, it was under 4 MB. Now after a
couple more weeks of dev, it is back to almost 6 MB.

#2: I have a routine that uses the Windows API to allow the user to browse
for the back end DB, then refreshes all the links (so that the BE can be at
different paths for different users; in one major implementation, some users
run it across a LAN, while others run it locally on a terminal server; both
are sharing the same BE). I just distributed a new FE at about 5,600 K. After
refreshing the links, the FE size jumped to about 7,400 K. Why?

Should I add an automated compact/repair to the FE? If so, what is the best
practice? At each close, or on a daily/weekly basis?

 

[Allen Browne]

Suggestions:

1. Decompile periodically.

2. Be especially careful of modifying the same file with different versions
of Access. Each uses a different binary. Always decompile before switching
(at least before switching backwards.)

3. Make sure the Name AutoCorrupt boxes are unchecked under:
Tools | Options | General

4. Instead of always running the reconnect code, run it only when the path
is invalid (which is easy to test with an OpenRecordset.)

5. IME, A2002 seems to be the worst bloater.