Error 1004 "Document not saved" when Closing File WITHOUT CHANGES??

A client of mine encountered this runtime error 1004 "Document not saved" today (while running a macro that opens, copies data from, and then closes [WITHOUT changes]) a series of files from a selected folder.
I am clueless as to how a Workbook.Close command (with SaveChanges set to FALSE!) can possibly cause this error. Any ideas?

Error 1004 Image.png

Error 1004 Debug Image.png

Following the code in step-by-step mode, check the variable …

Originally Posted by Marc L

Following the code in step-by-step mode, check the variable …

Check what variable? OpenedFile? That is set to the workbook that was opened (and the macro is now trying to close).
Regardless, why would we get a "Document not saved" error when the VBA code is NOT attempting to save anything??

I should note that the macro typically runs without issue. This was a seemingly "random" (unusual) error, but I'd still like to understand what might have triggered it.

Yes, Mark is referring to the OpenedFile variable. You should carefully check whether the expected workbook is assigned to the variable. It is also puzzling that the message appears when Excel's own error handling is enabled (it is only two lines down that you disable handling). But it is also possible that it has already been turned off before the line

Please Login or Register  to view this content.

It may be that this is a "temporary indisposition" of Excel and in a while everything will return to normal. You can also, just to be sure, add one line of code, which seems unnecessary, but it won't hurt either

Please Login or Register  to view this content.

Several times I have encountered strange errors generated by Excel, especially when our task is to process data in a loop.

Artik

Thanks, Artik. Maybe it was just a fluke of some sort. But I'm still wondering why Excel would throw a "document not saved" error, when there is nothing in the code telling it to save the file!

Therefore, if an error occurs, you should check what the OpenedFile variable contains. And only with this knowledge can you try to make conjectures.

In my opinion, you should write this piece of code so that when the line

Please Login or Register  to view this content.

is executed, its own error handling works. This could be simply ignoring errors

Please Login or Register  to view this content.

Then the file will probably be closed without saving and without an error message. These are just my guesses, this should be investigated in depth.

Artik

Well, this is not a crucial issue. I'm just curious about what could have caused it.
The value of OpenedFile should not be an issue. The code runs a loop that opens each file (setting OpenedFile=ActiveWorkbook immediately after the open event), and then closes it (via the code in question) before opening the next file.