I have a workbook out in the field that is 3.5-4 MB, depending on how
compiled the VBA is. Right now I am getting complaints of it crashing
Excel. The solution is to close Excel without having it try to recover,
then do an Open and Repair on the last saved file. But, of course, users
don't like this.

The Open and Repair leaves it with no compiled code. I can run a VBA Code
Cleaner and achieve about the same thing. Or I could clean the code and
then fully compile before I release it to the field. Right now it is
semi-compiled, meaning I have not hit the compile menu selection since my
last clean, so only the popular VBA code has been compiled when it was run.

So my question is what can I do to maximize its stability?

Don <www.donwiss.com (e-mail link at home page bottom).