"Save changes in <filename>" prompt even if no changes are made

When you close a workbook in Microsoft Excel, you may be prompted to save changes to the workbook even if you have not made any changes

This behavior occurs when something in the file has changed. Many times the user doesn't realize there are elements in the file that have been updated or calculated. Here are some examples of common scenarios:�

• There is a volatile function used in the file. Examples of volatile formulas are listed in the more information section of this article.
• The file has been opened in a newer version and formulas have been calculated. See article in the more information section.
• A formula that contains a link to a formula in another workbook and that uses volatile functions
• Linked pictures
• Iterative formulas
• Charts that are on chart sheets or that are embedded into worksheets but that have their source data in another workbook
• VBA code that updates the workbook

Because of this�automatic recalculation, Excel prompts you to save changes to the workbook when you close it.


Opening a file in a newer version
For more information on how Excel recalculates the file the first time it is opened in a new version see the following KB.
210162 Workbook loads slowly the first time that it is opened in Excel

Note: Turning your calculation will not stop a calculation of the file the first time it is loaded in the newer version of Excel.

Volatile Functions in Excel

List the most popular�volatile functions that maybe in the file.�Note: Setting your calculation option to Manual will stop this behavior but your formulas will not update as expected.


The CELL() function is not considered volatile in some situations, even though it causes this behavior.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Charts

When you close a workbook that contains a chart of any type, Excel prompts you to save changes to the workbook. This is because of the way that Excel handles charts.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.