MDLarson
Registered
I'm trying to setup a script in FileMaker 6 to automatically save a PDF file via Mac OS X's built-in "Save As PDF..." routine. It's pretty simple in FileMaker scripting terms; you just perform a sample save as PDF print, then go to the script and save the settings.
Anyway, when I run the script on my B&W G3 400 with 640 MB of RAM in Mac OS X (10.3.5), the pdf file is successfully created on the desktop. No errors.
But when I run the same script on an iMac G3 350 with 320 MB of RAM in Mac OS X (10.3.5), the print box pops up and immediately FileMaker returns an out of memory error: "Sorry, there is not enough memory to complete this operation."
I was under the impression that Mac OS X doled out all the memory an app needed and, in addition, turned on virtual memory when needed. I don't doubt that the real issue is memory, but why, specifically, is this happening? I opened up Activity Viewer and there was approximately 88 MB of free RAM. I don't like seeing out of memory messages.
Also, if I manually print to pdf on the iMac, it works.
Anyway, when I run the script on my B&W G3 400 with 640 MB of RAM in Mac OS X (10.3.5), the pdf file is successfully created on the desktop. No errors.
But when I run the same script on an iMac G3 350 with 320 MB of RAM in Mac OS X (10.3.5), the print box pops up and immediately FileMaker returns an out of memory error: "Sorry, there is not enough memory to complete this operation."
I was under the impression that Mac OS X doled out all the memory an app needed and, in addition, turned on virtual memory when needed. I don't doubt that the real issue is memory, but why, specifically, is this happening? I opened up Activity Viewer and there was approximately 88 MB of free RAM. I don't like seeing out of memory messages.
Also, if I manually print to pdf on the iMac, it works.