Front-end is growing rapidly - is an Office reference to blame?

[Larry Kahm]

I recently made a change to a front-end database because the site had two
different versions of Office installed. The fact that the VBA code was only
using one caused some workstations to function, but others didn't work at
all. I elminated the hard-coded references and am using late-binding.

Now, the FE is growing at a rather rapid rate - several dozen MB in a matter
of hours, with only a handful of users. Have I inadvertently caused my own
problem by removing those references?

Thanks!

Larry

 

[Allen Browne]

That should not be the issue, Larry.

Have you split the database, so each user has their own local copy of the
front end? That will probably solve it. If that's a new idea, see:
Split your MDB file into data and application
at:
http://allenbrowne.com/ser-01.html

If you have split, and still have the problem:
1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html
Then Compact the database to get rid of this junk:
Tools | Database Utilities | Compact

2. Using the *lowest* version your users will have, decompile a copy of the
database by entering something like this at the command prompt while Access
is not running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
The compact Access, and compile it again.

The combination of these suggestions should stop Access bloating due to
mutilple users saving the objects, Name AutoCorrect errors, or
auto-recompile caused by multiple versions.