Code corruption problem

[Patrick C. Simonds]

I have a problem that is driving me up the wall.

I have a workbook with an extensive set of VBA code. I can save the workbook
a hundred times and rerun my code with no problems but if it saves upon
closing Excel, the next time you open it and run the code it crashes Excel.
I have tried everything I can think of to fix this but Excel provides no
information on what is crashing the program.

Now I am wondering if I can suppress the save on exit prompt. No change will
be made to the workbook without going through a UserForm so I can run a save
routine when the UserForm is dismissed.

 

[JLGWhiz]

Don't know if it is the same problem or not, but I once had a file with a
bunch of numbers that calculated everytime the file opened. I had a bunch
of formulas that did averages, max, min and several other things for
statistical data. Excel decided one day that it did not want that file to
open anymore and put it in quarantine. I still have not figured out what
the criteria was that Excel used, but it refused to let me use that file
anymore. There must be something built into the system that counts the
number of times a file barfs for the same reason and then flags it, but I do
not know that for sure.