Saving Changes in Personal.xls

Every time Jason closes Excel, he is asked "Do you want to save the changes you made to the Personal Macro Workbook? If you click Yes, the macro will be available the next time you start Microsoft Office Excel." This is supposed to happen if he made a change to Personal.xls, but it happens even when he make no changes at all.

More than likely, this comes about because there really are some changes being made to the Personal.xls workbook. For instance, the workbook may have a dynamic function in some cell, such as Now() or Today(). These are updated immediately after opening a workbook, so Excel thinks there has been a change to the workbook. If such is the case, you will need to make Personal.xls visible and remove the dynamic functions. (This assumes, of course, that they are not needed by anything else in the workbook.)

Another place to look for changes is in any macros in the Personal.xls workbook. Pay particuarl attention to macros that automatically run when you first start Excel. These macros may be saving temporary information somewhere within Personal.xls, which Excel sees as a change worthy of possibly saving. Check your macros to determine if this is the case.

If this doesn't do it, then get out of Excel and rename the Personal.xls file to something else. Start up Excel and use the macro recorder to create a simple macro that you store in Personal.xls. This creates a new file, and when you exit Excel you should see the prompt asking if the save should be made. Make the save, exit Excel, restart, and exit again.

If the same problem exists, you know it is not because of the Personal.xls file, but due to another cause such as an add-in. You could then try some of the things in MVP Jan Karel Pieterse's article on solving Excel startup problems:

http://www.jkp-ads.com/Articles/StartupProblems.asp

If the new Personal.xls does not have the problem, copy all the VBA code from the old to the new and test again. If the problem is solved, you can delete the renamed version. If the problem returns it is something with the code, and you can repeat the renaming and retesting, checking each macro until you find the one causing the problem. Its code will have to be changed or deleted.