Yes, slowing the script down fixes the big problem of waiting for the PDF to actually be written to disk/memory in full before trying to append to it, and that goes for each additional Append step.
It might be worth including a 1 second pause after each step which actually writes to the file in the hopes that will let it complete each step before starting to execute the next write operation in the script.
Thank you Stephen, that seemed to do the trick. I'd never needed to try to slow Filemaker down before, but with how fast it fly through that PDF construction I had to wonder if acrobat/system/finder couldn't keep up.
In earlier versions of FileMaker, just a 0 second pause was enough to get over some timing problems. I'd be interested in learning if 0 second pauses would work as well as the 1 second pauses.
Yes, let us know.
When we were first able to program in fractions of seconds, I often used 0.1 seconds, which worked. I think the timed pause may simply be forcing the script to await completion of the previous step before continuing.