How are you creating the PDF with the Runtime version? It's my understanding that the only way a runtime solution can generate a PDF is by using a PDF utitility to "print" the PDF.
You are absolutely right - unfortunately.
I haven´t gotten that far, and mostly tested it in FM version. Only looked at it and tried a few basics in the runtime version so far and in the problem computer, we tried the print (with attached pdf) to see if the problem with the shutting down would behave different in the runtime, to find out if it was something with the two different FM versions.
Since the runtime was created in 9 and the problem computer has FM 8.5 installed - the runtime version wouldn´t be affected of that.
I thought it was mostly network features that was affected of runtime and unfortunately hadn´t studied the manual enough.
The problem is apparantley not the pdf-filen then, anyway. It is a printing problem.
Do you know what causes (both the runtime and FM pro) the programs to shut down when we try to print from the Vista problem computer?
In runtime on my Mac and the other Vista computer, a dialoge box appear with a message that the printout couldn´t be done, but the rest - the e-mail part - works and the programs keeps running.
I hope I'm understanding your original message properly. It's my understanding that runtime solutions cannot "save as pdf". As a Mac user I know there's probably a way around this by addressing the OS directly via Calculated Applescript and the "do shell script" command, but I can't speak to the Windows OS. This is one of the reasons I don't bother creating runtime versions as my software relies heavily on printing (saving) as pdf.
Thank you, it seems to be correct and it is a pity that it can´t create pdf´s of course.
My solution is however not depending on the pdf, but to send e-mail with automated information that is saved.
And that can be done on 2 test computors - one Mac and one Windows Vista - but not on the third one, wich is a Windows Vista machine. Then it just shuts down.
That is what gives the memory message in runtime, but not when running it in FileMaker. When in FileMaker, it just shuts down with no message. Have you heard of that before - FileMaker/runtime shutting down when wanting to send an e-mail through scripts...