Peter Lehrack Posted August 17, 2010 Posted August 17, 2010 Is it possible to email the contents of a SuperContainer (PDF's in my case)? If not natively, any workarounds? Thanks, Peter
agutleben Posted February 11, 2011 Posted February 11, 2011 Hi Peter.. You may already have your answer, but I thought I'd respond anyway. I came across your post when I was trying to figure out how to email files stored with SuperContainer via a FileMaker Server scheduled script. While some of what I discovered won't apply since you're using FileMaker Pro, the answer will also work for you. Here's a link to my post: http://fmforums.com/forum/topic/76527-attaching-files-to-server-scheduled-emails/ Cheers, Aaron
Smef Posted February 11, 2011 Posted February 11, 2011 Plugins don't work with FMGo, so you will need to use a server scheduled script instead.
agutleben Posted February 11, 2011 Posted February 11, 2011 Plugins don't work with FMGo, so you will need to use a server scheduled script instead. Of course.. sorry. Long night last night. Thanks for following up and catching my mistake. And.. as a plus.. the post I linked to will work as is.. Thanks, Aaron
Peter Lehrack Posted February 11, 2011 Author Posted February 11, 2011 As I use a hosting service for my database and it's on a shared server, I cannot use server scripting. :-/ Peter
agutleben Posted February 11, 2011 Posted February 11, 2011 As I use a hosting service for my database and it's on a shared server, I cannot use server scripting. :-/ Peter You could accomplish the same thing by using a dedicated workstation running FileMaker Pro which runs a looping script. It's not ideal, but can basically do the same thing as a scheduled script. There are some differences, but they're subtle. Aaron
Peter Lehrack Posted February 11, 2011 Author Posted February 11, 2011 You could accomplish the same thing by using a dedicated workstation running FileMaker Pro which runs a looping script. It's not ideal, but can basically do the same thing as a scheduled script. There are some differences, but they're subtle. Aaron Aaron, I have been mulling over that option but it doesn't seem to be worth the trouble and expense at this point. I really just need iOS to allow for emailing of pdf's. Thanks for the interest in this issue, Peter
agutleben Posted February 11, 2011 Posted February 11, 2011 Aaron, I have been mulling over that option but it doesn't seem to be worth the trouble and expense at this point. I really just need iOS to allow for emailing of pdf's. Thanks for the interest in this issue, Peter In that case, you are really looking at storing files in container fields. There are many reasons why this is not ideal (of which you may already be aware), but if your need to email these files is greater than the issues presented by using container fields then perhaps it's the way to go for you. I always try to look at the big picture when implementing features because expense occurs either way. While you may not have the upfront fees, your solution may take a performance hit, an increase in storage fees can occur as backups grow much more quickly when storing binary files in FileMaker, etc.. I'd also argue that an email process run natively on the iOS can take more time than if you were to hand that off to a server or dedicated robot machine. And what happens if your iOS device loses it's connection? Anyway.. It sounds like you've been over these thoughts before. There are lots of things to consider. Good luck! Aaron
Peter Lehrack Posted February 11, 2011 Author Posted February 11, 2011 Aaron, I store several gigabytes worth of PDF's which is why I use a hosted Supercontainer service (360works, to be exact). This setup works very well for 99% of my operation, I just want the ability to send out stored pdf's during after hours/weekends while I'm on the go. The current iOS/FMGo setup allows me to open the pdf or view it via iOS Safari, tantalizingly close to fulfilling that last 1% of my implementation. For now, during off hours while I'm on the go, my customers just have to wait for resends. Peter
Smef Posted February 14, 2011 Posted February 14, 2011 You could set up a robot machine using our Remote Scripter plugin which would listen for triggers from your FileMaker go. This would prevent you from having to use a looping script, though you would still need the FMPro client up and waiting. http://360works.com/remotescripter/
Recommended Posts
This topic is 5029 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now