thisworkbook.saved changes inexplicably

Problem
I set a conditional break point for every change of the variable thisworkbook.Saved in any routine of any module.
I set thisworkbook.Saved=true from the immediate window.
Immediately after, without doing anything else, I press x to close the file
=>
the value of the variable becomes false before executing any line of VBA: the trigger takes me to the header of the before_close



NB if instead of setting the value true to the variable .saved I do a save the problem does not occur: that is, by pressing x the variable .saved remains true

Any suggestions?

My program contains tens of thousands of lines of vba and sensitive data so I can't send it, I would like to know if anyone has experienced a similar problem and the relative solution
alternatively if you can suggest a path to follow to try to understand who / when / how the variable is modified.
Perhaps there is some other parameter that a real save sets besides the .saved variable that then gets looked at?

thanks Kaper for the suggestion, unfortunately I tried without getting any changes
It seems like there are some suspended actions that start when you press "x" (it's the same if I proceed via menu)

is there any other test to do?

Are there volatile functions in the sheets?

Artik

Check in the immediate window whether the state was set.

e.g.
?thisworkbook.Saved
False
thisworkbook.Saved=True
?thisworkbook.Saved
True

Sorry for the delay in responding I had some small personal problems.
Yes unfortunately there are volatile functions (including conditional formatting)
Ok they are volatile but as said after setting the saved status to true I do not perform any action, why do you assume that a recalculation of them starts?
How can I act?

Sorry for the delay in replying, I had some small personal issues.
Yes, if I print the value of the saved state after setting it, the system correctly returns true

@Artik
Considering my answer, Have you any suggestion?

Unfortunately, not having access to the file, I have no way to investigate the cause of this behavior.
I only suspect that the reason may be conditional formatting. The only thing I can advise is to create a copy of the file, remove all conditional formatting from the workbook. Now investigate if the problem still occurs. If there is no problem, it will indicate that the “culprit” is the conditional formatting (or more precisely, the formulas used in it).

Artik

Thanks Artik,
I followed your advice but unfortunately even the file without conditional formatting behaves the same way

I managed to narrow down the problem.
Attached is a very simple file with which to reproduce the bug
1) open the file
2) manually change the size of the button by pressing the button with the square (the design mode)
3) from the immediate window launch

Please Login or Register  to view this content.

4) optional, verify that this has had an effect by typing

Please Login or Register  to view this content.

it will answer "True"
5) try to close the sheet
6) it will ask if we want to save the changes!!!
7) answer Cancel
8) type

Please Login or Register  to view this content.

again, it will answer "False" !!!

If instead of the command 3) you do a real save all it will work as expected (i.e. at point 6 the file will close without any questions)

So what else must be done in VBA to fully simulate the Save command?

I confirm that this problem occurs. But, unfortunately, I am not able to understand and explain it.

Artik