This same exact behavior happens when trying to cancel out of a FIND of unstored fields (like an unstored calculation field or a related unstored calculation field).
I think that every developer would agree that this is the #1 biggest ongoing, unfixed problem in FileMaker.
annoying, very annoying - but nit the 'biggest' because it doesn't destroy anything (compared with the FMS that doesn't close files in some circumstances and the 'importing-bug' that leaves untouchable scripts/cf after importing)
and the 'importing-bug' that leaves untouchable scripts/cf after importing)
I maintain a public list of confirmed bugs here in the forum. I don't recognize that one. Feel free to share a link or make an issue report of it as it sounds like a biggie.
Thank you for the post.
Our Testing department had a previous report (not through the Forums) of this issue. I've added the comments on this thread to the original report. No additional information is available at this time.
TSFalcon, I do recall previous issue reports here in the forum describing this issue. Perhaps no TS person saw them?
An entry linked to this report has been added to the Known Bugs List. Please post any comments/questions/concerns about that entry either here or in a new thread. Please do not post a comment about it in the Known Bugs List.