You might try using 2 paragraph returns with a space between them (all in quotes) to force double spacing, unless this makes the working email systems look awkward.
At least see if it works or if the returns still get stripped by Outlook.
I had a similar problem on mac - the solution is for both mac and pc.
I have a table where the user can create email template messages with merge fields. Then they choose the template for the email they want to send, and the script substitutes the merge fields with data from each record in the global field, then sends the email with the global field as the body text.
If I put the actual text in the email body part - I had the same problem as you with Apple Mail and I had to use extra quote marks and paragraph returns to get it to work. But with the global field, I do not have to do that. I just set the global field with the merge field substitutions to the template body field WITHOUT any extra paragraph returns or quote marks. The global field text was not formatted any special way. Then I had the email script use the text in the global field. Voila - double and triple returns were retained properly.
Can't say why it works - I believe FileMaker retains the contents of a field differently than the contents of a text box and that is why. But it is much simpler and easier for the user.
Hope that helps
I saw this a while ago and made a note as I have a few customers now using Outlook on the Mac:
FileMaker 8/9/10/11 Certified Developer
- - - - - - - - - - - - - - - - -
Phone: +61 2 9484 6565
Mobile: +61 418 468 103
Thank you for this. I am back with client end-of-week. He will be delighted!
Thanks to all who offered solutions. Will let you know how I get on. There must be a lot of frustrated Mac/Outlook users out there!
I find that Outlook for Mac 2011 v.14.2.5 is unrecognized by FileMaker as a MAPI client. My scripts that send mail using the Mail Client work fine if I specify Apple Mail as the mail client. But if I specify Outlook as my mail client, FileMaker cannot dispatch the email and no error number is reported in the Debugger. It just skips the script step altogether.
What version of FMP are you using? One possible problem is your version of FMP.
See FMI Knowledge base article # 7955
FileMaker Pro 11.0v3 will not Send Mail with Entourage 2004 as the default mail application
I've had several problems with Outlook 2011 for Mac interfacing correctly with FileMaker. Eventually I wrote custom AppleScripts to take care of the problem. Contact me back channel if you come to needing something like that.
FileMaker 12.0 v3
Outlook for Mac 2011 v. 14.2.5
Mac OS-X 10.8.2
I tried it on my computer and the FMP script step Send Mail worked fine both with and without dialog. Could you double-check that Outlook is the default mail client?
Outlook Mac 2011 V14.2.5
Mac OSX 10.8.2
You are right. My error. I was on FileMaker 120. v1 I upgraded it to v3 and the problem disappeared.
thanks to all.
Oh Dennis... what do you mean not being on the latest version <cynical grin>. --- just giving you a hard time!
Speaking of the latest version... on the server side... if you got a license from FileMaker this last week, they are still sending out links to download FMS 12.0v2 and then you have to install it and then download the update and install it. I sure hope FM puts the real FMS 12.0v3 on their software license links for new customers soon because it is a hassle also having to do the upgrade.
The only thing I got recently from FMI regarding the server is the news about the Java update. That seems to be a settled matter now.
Regarding being on the latest version - the fact is that I WAS ON V3 -- until that nonsense about creating PDFs crashing the app required me to reinstall and I neglected to go from v1 to v3.
If I had to stand corrected every time I was corrected I would never sit down.
Oh, good for you that it worked this way.
We do have a customer site where just the same problem pops up. FM12's ( also 12.0.3) "send mail" step will trigger MS Outlook (from Office Mac 2011, 14.3.0) - since that is the choosen mail client on the system - but does nothing more.
It seems to be a problem of the two applications not adhering to the same standards of communication. I checked the Applescript from Tim Cimbura, that reveals the way Outlook wants to be told... Will try that as a work around.
A quick fix for me was to send the body/message text wrapped in the GetAsCSS() function.
Bye for now