|
#1
| ||||
| ||||
| FileMaker 6 on OS X > "not enough memory"? 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. ![]() |
|
#2
| ||||
| ||||
| Weird... have you tried actually creating the script on the iMac instead of using the one you created on the B&W?
__________________ Power Macintosh G4/500MHz "Yikes!" 10.4.11 Server • 1024MB • 3 x 120GB + 320GB • DVR-111D • 2 x Radeon 7000 PCI • 2 x 17" CRT MacBook 2.0GHz Core 2 Duo - White 10.5.5 • 2048MB • 80GB • CD-RW/DVD-ROM iPod Photo 60GB • iPod nano 1GB • AT&T DSL 6Mb/768k http://www.jeffhoppe.com |
|
#3
| ||||
| ||||
| Hmm, well, no I haven't. I can't imagine that making a difference, as the successful act of creating the FileMaker script is directly related to the success of the print, as it can create the PDF via the manual process just fine... It's probably worth a try though. Computer problems can be horribly tough to nail down. |
![]() |
| Thread Tools | |
|
|