Weird Sizing Issue

[Superock]

I have created a dB with a Front End and a Back End.

The front end only holds forms and reports, the weird thing is that when a user uses the forms and then closes the dB later the size of the front end increases. (Significantly)

Any thoughts?

 

[Crilen007]

the front end downloads the back end data when it is being used.

If you want to shrink it again, you have to compact and repair it.

 

[Skeletal]

Compact automatically when the user closes the front end. In the Access db window go to Tool/Options/General and tick the box "Compact on close".

Skeletal

 

[The_Doc_Man]

This would occur if there is an intermediate query (a query of a query) and the FE is on a different machine than the BE.

OR if there is any form that dynamically creates a query "on-the-fly" when you request a lookup

OR if the user has the ability to create queries in the FE

OR if you failed to save the FE with compiled code (i.e. just save it with VBA as text). When you open it, the FE has to compile the code before you can do anything.

OR if any VBA code can do a MAKETABLE (such as importing data) and you didn't specify where it would get made...

 

[Superock]

This would occur if there is an intermediate query (a query of a query) and the FE is on a different machine than the BE.

OR if there is any form that dynamically creates a query "on-the-fly" when you request a lookup

OR if the user has the ability to create queries in the FE

OR if you failed to save the FE with compiled code (i.e. just save it with VBA as text). When you open it, the FE has to compile the code before you can do anything.

OR if any VBA code can do a MAKETABLE (such as importing data) and you didn't specify where it would get made...

Is it bad practise to do a "query of a query"?