Fst1 and T. Valko,

Thank You - This worked perfect - I really appreciate it.

"SteveDB1" wrote:

Hi all.
Forthe past 6 months, I've been working on a single workbook for a large
project I'm doing.
About 3 or so months ago I noticed an error when I opened the workbook.
The error states that the workbook must be recovered due to a calculation
error that has occurred.
Since I'm the author of the file, I click ok, and mosey along my way.
Last month, I decided to look into the issue farther, and found that some
worksheet function formulas that I'd written were linked to an earlier
iteration of the workbook.
I found and deleted all of those older, externally "linking" formulas.
It resolved the issue for about 3 weeks. This last week, the issue started
again.
When it happens, I click ok to continue, and it calls up a small window
telling me which worksheets were "corrected" to resolve it.
It also shows a "calculation properties.xml" file.
When I open that it really doesn't tell me anything that I can use to
resolve the issue. Oh, excuse me, it tells me which worksheet is responsible
for the error.
Once in the file, I open the VBA editor to determine the sheet name to see
if I can identify the problem.
When I go to the worksheet and study the formulas I'm not able to find
anything that would make it clear why this is taking place.
There are no externally "linking" formulas, or complex formulas that I can
readily identify.
The next thing is that the calculation property "errors" are not
consistently the same worksheet. It literally changes from day to day.
Also I think of importance is that I'd initially decided to save this
workbook as an XLSM file because the next phase of this project is to create
a macro to auto-update the worksheets within the file from another server
location.
My questions:
1- has anyone had this happen before?
2- if so, any fix?
3- if not, any ideas on what might be causing this to happen? (and yes,
provide me with an email, and I will take screen shots to demonstrate what
I'm talking about.)
4- could the XLSM format be the cause? Until a moment ago I didn't even
think that might be "part of the cause."
If this is not a good enough explanation, please let me know, and I'll try
to clarify further.
Thanks for your time.
Best.