Is there a real need to 'embed' the file in filemaker pro? Why not store a reference to the file? This would make your solution file size much smaller.
Version 12 looks promising for such a task.
I have done the same thing with version 9, using stored file references to the pdf. If you wanted to view the pdf within filemaker, you can do so via the web viewer on a layout.
Can't say I've done anything like this with IWP, so I can't help you there.
We have done it both ways. Some of our solutions store references to the file and some are embedded using the the SuperContainer PlugIn. For web we have always gone with the SuperContainer as it prevents users from downloading the file without logging into the database.
Yes. Forget inserting PDF files set for external storage in FileMaker though. It doesn't work in FileMaker 12. Not for practical uses anyway.
Use a plugin like Dacons FileFire to handle file management from within FileMaker as needed, while keeping your files in whatever shared volumes/drives you need them to be depending on your environment.
Curious ADNPlus, why do you say it does not work in FM 12...?
The behavior is different when using a stand alone FileMaker file and when using the same file hosted on a server. When hosted on a server all pdf files inserted into containers are copied to a location relative to the database in the server pc and not in the volume/directory where you really want them. This means that you would need to have an external method of moving files between that FileMaker server directory and the target directory where you really want the file to be. For example, your network users typically share a volume for file storage, but none of them are likely to have access (nor should they really) to the FileMaker server database folder where the PDF files are placed by the container behavior in the hosted database. Because of this implemetation, which I find flawed, FileMaker in fact, continues to encourage files being embedded in a FileMaker container but not stored outside of FileMaker. This may be impractical for organizations storing a lot of files. My guess is, most of them.
I spoke to FileMaker support about this behavior and they confirmed that it was not documented in their knowledgebase then, and I have not checked to see if it has been updated since. Gosta keep rollin' with the punches I guess, I have a production schedule to complete.
Storing as a refrence would be ok though...right?
something I noticed last night was with a pdf that was displaying on a layout is that if you (in layout mode) optimise the image for jpg etc, this is perfect for printing, as it removed any stupid pdf tools or borders, however, it only works on the Mac, on windows it just showed the icon of a pdf file. If I change it on the layout to "interactive"- (pdf etc) then I can see it on both platforms, but with borders and pdf tools. UGLY.
This is FM 12 v3 on all workstations.
Sorry, my first post was confusing (I've edited it for clarity). I meant, storing image by reference should be okay as in using the import folder command. But, test it on your expected scenario, be it stand-alone FileMaker file, or hosted database. I must say I do like the ability to have some more control in containers, I like that after countless years we finally have drag and drop on containers. As for the interactive function, I think that sizing the container field appropriately should take away the uglyness. Basically it's impossible to interact with a PDF if it's contained in a stamp sized field. Cheers.