My guess is you have what's referred to as 'database bloat'. You probably
just need to do a compact and repair, then a decompile, then another compact
and repair. I do this on a regular basis and it keeps my app to a reasonable
size. Beofre I knew about the decompile, I just did compact and repairs, and
over time my appl got up to 80MB! Now it's around 8MB, and it's a good-sized
application. When I do a compact, I make a copy of the DB beforehand. Then
open Access (not the appl) and go to Tools, Database utilities, Compact and
Repair Database. I always compact to a new DB and keep the old copy around
temporarily just in case. Then, after the compact, do a decompile. I have a
..bat file with my decompile statement in it. I edit it whenever I want to run
it and put in the appropriate file name. Just double-click the .bat file and
it will start the decompile process - this opens up a DOS window, then opens
up the access DB. The decompile statement should look like this:
"C:\Program Files\Microsoft Office\Office\MSAccess.exe" /Decompile "DB
filename"
After the decompile, close the DB, then do another compact/repair with the
decompiled DB. You should see a much smaller DB size. Someone else could
explain exactly why bloat happens, I forget the exact reasons, but I know my
DB grows quickly and I do this process jus about every day.
