AppleScript problem after last silent security update

TomKa wrote:

I am not an experience scriptor. Hence I can accept the advice. However:

– as I have said: in my experiment I have tried to delete the file stored by the first execution before making the second attempt. The second attempt has nevertheless failed.

– using my document with the full script has always worked, independently of deleting an existing file with that name beforehand.

Perhaps the problem is in the RagTime 7 app. You and I both were thinking in terms of straightforward file saving behaviour. But I can assure you that nothing of the sort exists. Saving a file in most apps is a convoluted process of creating a temporary folder, saving a new copy of the file therein, then swapping out the new file for the old, and then deleting the temporary folder.

Furthermore, after doing that, the "document" is assumed to then be represented by the saved file. I think you are attempting a save from file A to file B.xlsx. Then you attempt that again and it fails. But the second time, it isn't trying to save A to B.xlsx. It is trying to save B.xlsx to B.xlsx, which may or may not succeed.

It is always possible for an app to simply create a new file with data at a given location. That's what you are assuming. But in the modern world, all architectures are Rube Goldberg architectures.

You can try to debug the script and see what RagTime 7 itself is doing when it saves this document. You might get a more meaningful error message. Maybe there is an "export" command you should be using instead.

If all else fails, contact RagTime 7 support. They claim that their product runs "flawlessly" on macOS Sequoia. In situations like this, when an app like RagTime doesn't work on macOS, most people will ask, "what's RagTime?" That will tell you where the problem lies. If it is a macOS problem that affects 80 million people, then it's Apple's problem to fix. But if it only affects RagTime users, then it's RagTime's problem to fix. Such is the state of the world today.

TomKa (author)

Perhaps if you may mention the newest Apple macOS update

to the developer from the point of what was changed and the

listed bits that are truly different going forward, they may fix it.

This document from Apple Support was included as link from

their Apple security releases - Apple Support but is separate.

"This document describes the security content of macOS Sequoia 15.4."

The linked item found within has related bits of interest:

macOS Sequoia 15.4 • macOS Sequoia • 31 Mar 2025

Might I suggest if a deeper look for any other ideas, might

make a better upgrade to their software. An action needs

address; or, if Maker's product is pending a newer release.

Yet sometimes my ideas get far ahead; or just off-course!

While I'm less affluent &/or poorer; in no rush to upgrade.

TomKa wrote:

My suspicion is, that the last macOS „silent security update“ (distributed last week) causes the problem.

Maybe it merely "exposed" an existing problem.

Your script is clearly wrong. What happens when the file "Daten.xls" already exists? This is an error condition. When you don't explicitly handle such error conditions, the behaviour is "implementation defined" and that implementation can change at any time, with no warning.

If the "Daten.xls" file already exists, then delete it first. Then save the new file.