After compacting a particular database, its filesize grows from a user simply logging on, opening/closing a bound form (without changing data), and logging off. For example: Post-compact size = 393,244 KB
- First LogOn/OpenAndCloseForm/LogOff increases size to 393,272
- Second LogOn/OpenAndCloseForm/LogOff increases size to 393,324
- Third LogOn/OpenAndCloseForm/LogOff increases size to 393,328
(Size stops growing at this point, regardless of any additional LogOn/OpenAndCloseForm/LogOff.)
This particular form displays 1,000+ actual records, and four bound subforms that also display actual records. The mainform and subforms use query definition objects as their record sources. Similar behavior occurs with other forms.
The environment is 64-bit Windows 7 hosting 32-bit Access 2010 and an unsplit, legacy 2002/2003-format MDB with ULS.
Is this behavior expected, given the internal mechanics of Access? If not, what might be causing it? Any reason for concern?