Hi Frank -- before I try this, I wanted to report two things and see, again, what you suggest.
I tried the earlier "final change" script five times. The way I ran the script varied slightly: the first time I pasted it into the Applescript Editor, compiled it, and ran it. I then saved it as an app, and as a script. My second time-out came when I ran it as an app (and changed to running on a different library). I did not use the app again. The other times I have run it either by pasting into a new Applescript Editor window, compiling, and running, or opening the saved script in the Applescript Editor and running it. (I mention all this because I don't really know what I'm doing.)
Each time I ran the script there immediately appeared in a Finder window a text file with the name given in the dialog box the script produces (I have in every case used the default). The first time, on a medium-size Library (1,200 Projects), the script finished instantly. Finder reported the text file size as 54 KB. (I just ran the script again on that Library with the same results.) When I run the script on my large Library (>20,000 Projects), a text file also immediately appears, but Finder reports this as "0" bytes. Then, eventually, I get the time-out error report from the Applescript Editor. I thought the immediate posting of the zero byte file was worth reporting.
The medium-size Library in on my system drive. The larger Library is on an external USB-3 drive mounted through a powered hub (I have no problems running Aperture).
The other thing I wanted to report, is that after running the script on my larger Library, when I then close the Library, Aperture reports that it is "Updating the Library" and presents me with the usual progress bar in percentages. Updating the Library takes about an hour. I do not get the "Updating the Library" action on the medium-size Library.
I confirmed that opening, using, and closing the large Library does not give me the "Updating the Library" action when I don't run the script. (I can't report what happens when I run the script and it works, as I haven't had this happen yet on the large Library.)
One more small thing (I suspect this is unremarkable) -- after the script times out, I have to close the Applescript Editor in order to delete the empty text file. Just to remove outside variables, after the first time-out error I have rebooted each time before running the script
Thanks for your continued attention 🙂 . Let me know of any suggestions. I will attempt the new "long time-out" script, but probably not until tonight.
Cheers,
--Kirby.