This is an old weakness of the system print queue management (Mac and Windows).
The rule is: don't create (a lot) more print orders than are being actually printed.
I recommend to add a pause after each print order to give the system a chance to finish the job.
Are you really creating 125,000 PDFs? If you do the math, even a 1 second pause would add up to 35 hours, which exceeds one day.
Please note, it's the number of print jobs that crashes FileMaker, not the number of pages.
Why looping? Can't you make a selection that you then print in one job?
Huslik GmbH • Bgm.-Widmeier-Str. 42 • 86179 Augsburg • Germany
CEO Winfried Huslik - HRB Augsburg 12386 - VAT-Id. DE127485099
Phone +49 821 565606, Fax +49 821 565001, Email email@example.com
Verify your FileMaker Pro files with FMDiff - http://fmdiff.com
I wish it could be a single print job (or a couple of print jobs). The client is taking all of the FileMaker data and moving it into a content management system. The client is using PDF as the file format. Each record has to be an individual PDF file. Turns out there are just under 153,000 records across 4 databases. All of the records create a single page PDF. All of the file names are being generated dynamically based on information in certain fields.
I'll try adding a pause and see what happens.
See how short a pause you can get away with. If 0.1sec is enough that cuts it down to 3.5 hours instead of 35, which would then be a feasible overnight job.
Looks like a 0.1 pause may do the trick. I'm watching FM loop through. Seems so damn slow now though. I've hit 2600 so far and no crash. That's further than its gone before in a single pass.
Thanks all for the tips.
FileMaker 13, OS X Yosemite. 16 gb of RAM in the system. Not hosted.
You may want to host the file to give yourself protection from crashes on the client...
Spoke too soon. Made it to 4680 records and crashed.
It appears that pausing targets the issue. Another thing to try would be a longer pause every thousand records or so. 10 to 30 seconds? I'm not an expert on memory issues, but it seems like this might allow both FMP and OS processes to resolve. Not a ton of total time added to the processing.
I know that both Mac and Windows file systems can choke on large file counts. Are you controlling the path so that a single folder isn't overwhelmed by file count?
I've got it set to a maximum of 500 PDF files per folder. That part works well. I'll try adding the second pause after every folder group.