Why the size of FE changes? (1 Viewer)

[Sun_Force]

I saw this post and it made me wonder why the size of a FE changes.
When all the tables are in sql server or another Access database, and users use FE to input data, why the size of FE grows and it needs to be compact and repaired?
There's no design change, there's no table to keep the data. But still the size of FE changes.

 

[theDBguy]

Are there any temporary tables or Make-Table queries in the FE?

 

[Sun_Force]

Except sys tables, not even a local table.

Edit: also no Make-table query. Even in vba.

 

[The_Doc_Man]

The FE is the place where Access makes lists of the records involved in queries. Remember that FE queries are evaluated in the FE. These lists of records are in some place inside the FE that we don't necessarily know in detail, but it IS a work space and, if the list is large enough or gets complex enough, it affects the virtual size of the FE. If THAT happens, the physical size of the FE has to grow to match it.

For that matter, forms and reports have .RowSources and .RecordSources and other kinds of sources that could be queries. If that happens, you have a behind-the-scenes enumeration of the records Access will touch (potentially). Again, these should be relatively small, but growth of the FE to hold these things that enter virtual memory is the most likely explanation.

 

[isladogs]

When code in the FE is compiled (usually on the 'fly'), the compilation code increases the size of the FE database.
You can see this very clearly by First decompiling then compacting and closing your FE.
When you reopen the FE the size immediately increases slightly as the code used in the startup form/procedures is compiled on first use.

 

[CJ_London]

with regards 'this post' the OP has not split his db so they do not have a 'front end' as such.

There should be no need to compact/repair a front end unless they contain tables, temporary or otherwise or the file has been modified in some way (new/changed object). In the latter case, it is just good practice since most of these sorts of changes would have minimal effect on file size

 

[Pat Hartman]

If you use embedded SQL rather than querydefs, Access needs to "compile" the SQL each time you run it to create an execution plan. This workspace can't be recovered until you compact the database.