Is there a manner to which multiple pdf files stored in individual container fields could be automatically printed via a script? We are attaching pdf images of our products to our invoice database so that we can quickly find and print an image if necessary. But I think it would be nice if the database gave you the option to view and print all the pdf files which relate to the invoice you are producing in a single step. Is a container field the proper way to go about this. Or are there any plug-ins which may perform this type of activity? Thanks!!

Have you printed any PDFs from FileMaker 7 container fields on OS X? They are low resolution, to be kind. Hopefully this will be remedied, but they're quite unusable now (at least on an inkjet printer; don't know about laser printers).

So that leaves opening the PDF (stored as reference) or exporting the embedded file. Either of which could be done with just FileMaker. But if you're talking about printing without a dialog, especially several at once, then you'd have to use AppleScript, or a plug-in.

How did you put these into the container? That is always a critical fact, which we need to know. Or are you asking what the best way to do that is (not that we necessarily know, but we could at least try in the right direction)?

We've been right clicking (os x) on the container and choosing insert picture. Then exporting file and opening it. The nice thing is that we can preview it (low rez) in filemaker but when it's exported it's regular size. I considered an applescript but I read somewhere that a photographer was using FMP6 to store and create a photo album so I thought maybe it could be applied to this sort of use.

The advantage of using AppleScript, or a plug-in, is that you can then Export Field Contents to a known location (such as the Users/Shared folder, then rename the picture back to its original name and open it; or just open it,* but without the "where do you want to save it" dialog. Or, like you said, export several pictures one after the other, renaming as you go, then printing them.

*If you don't rename it, you can only export 1 at a time, I imagine. I don't know what would happen if you tried to export another while the first was open in memory. If it didn't error, you'd be overwriting the file on disk while its image was open. Doesn't sound very stable, even if allowed.

I'm hoping that someday FileMaker will allow commands like ExportFieldContents to allow a calculated file path; but I'm not holding my breath. It's pretty easy to rename it.

I don't know exactly how the photographer was using FM6. But I can imagine. The trick is, as you've found, making the images easy to add and use in both the database and externally. There are also size and networking considerations; though with 7 one can finally say, "size doesn't matter" :-)