We've been using the "Email Plugin 1" for some time and we are trying to switch how attachment files are stored -- to FileMaker's remote storage container.

 

When we attach a PDF that has been stored in a container field, the email recipient cannot open the PDF -- it seems to not be a valid format -- they can't be opened.  Same with Word docs.  However, sending an Excel file worked.  

 

We've experimented with PDFs we've made and PDFs made elsewhere.

 

When we download files from the container (versus emailing it), the file format is valid and opens ok. 

 

When we attach the file, we are calling the plugin's function:  EmailAttachFile ( ATTACH::Attachment )

 

Any ideas on what we can look into?

 

 

Update:  I found a workaround.  Exporting field contents to temporary folder and attaching it from there results in usable files.  I wonder why we can't use the step with the remote container field.

Well, it works for me very nicely both on a Mac and Win machine. I can easily pick up the contents of a container field and attach it to an email message and then read it when it arrives. The container fields are note remote, however, in case that makes a difference in the behavior of the plug in.

 

I have been writing container field contents to a file, but now I'm going to start using this technique.

 

Anybody know how to export a Filemaker report to PDF and insert it into a container field without writing it to the file system first?

 

Gary