Hi Jacob,
There is nothing in the macro to cause a file save.
You must have something else going on, but I don't know what.
The macro you chose is a regular macro and works off of a
selection of cells, as opposed to the event macro below it.
I see from the previous reply that you must have installed all
of the state codes into AutoCorrect, and I don't see how that
could causes saving either.
All I can suggest is to complete exit Excel and try it again.
If you get into Excel and run the macro, rather than just stopping
try DeBug and see what statement it is hung up in -- hopefully,
for me, it won't be my macro.
Right click on the worksheet to see if there is code there.
Rigth click on the icon to left of the menu bar which bring up
"ThisWorkbook" and see if tehre is cde there. Use the [x] in the
upper right corner below the [X] that closes the Visual Basic Editor
to get out of the module.
If you have macros you should set the security to "Medium",
and reply each time you open the workbook. This is for your protection
against opening an Excel file without even realizing you opening an
Excel file, or in opening an Excel file that is not supposed to have
macros -- it gives you a chance to look at the macros. Setting the
security to "High" which is the default prevents macro use altogether.
When you change the setting, you have to exit the wrkbook and open it again.
--
