![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello, My runtime solution will not send the attached pdf. When the file is a filemaker file, the button I assigned to create an attachment in pdf format works properly. But when I create a runtim solution, the button does nothing. Is there an extension I need in order to make this work? Thanks. |
#3
| |||
| |||
|
|
PDF creation is not supported in the runtime version...unless you already have an external PDF program you can print to. Sert Ian wrote: Hello, My runtime solution will not send the attached pdf. When the file is a filemaker file, the button I assigned to create an attachment in pdf format works properly. But when I create a runtim solution, the button does nothing. Is there an extension I need in order to make this work? Thanks. |
#4
| |||
| |||
|
|
Hello, My runtime solution will not send the attached pdf. When the file is a filemaker file, the button I assigned to create an attachment in pdf format works properly. But when I create a runtim solution, the button does nothing. Is there an extension I need in order to make this work? Thanks. |
#5
| |||
| |||
|
|
Page 90 of my FM8 Advanced Developer Guide lists the script steps that are IGNORED by the runtime application. The list includes "Save records as PDF" ! As it turns out, this is going to be a nuisance for me as I am currently working on a layout that uses container fields to create a colour-coded diagram (actually crash test dummies). I have already successfully exported a trial result as a PDF. I was intending to have this feature in a runtime version but Ian's experience suggests this will not be possible. This is a serious limitation to runtime applications and makes Advanced version less attractive for developers. |
#6
| |||
| |||
|
|
So the addition of pdf support in FM8 is pretty anti-climactic anyway, and its loss in runtimes even more so. Although, I agree with you that it *is* annoying. |
#7
| |||
| |||
|
|
In article <436bd0e9$0$22880$afc38c87 (AT) news (DOT) optusnet.com.au>, mpaine (AT) tpgi (DOT) com.au says... Page 90 of my FM8 Advanced Developer Guide lists the script steps that are IGNORED by the runtime application. The list includes "Save records as PDF" ! As it turns out, this is going to be a nuisance for me as I am currently working on a layout that uses container fields to create a colour-coded diagram (actually crash test dummies). I have already successfully exported a trial result as a PDF. I was intending to have this feature in a runtime version but Ian's experience suggests this will not be possible. This is a serious limitation to runtime applications and makes Advanced version less attractive for developers. Not really. Beleive it or not most users of Advanced are in it for the script debugging, custom functions, etc... not for runtimes. That said, Mac's can create PDFs from any print job, and you can get free software to do same for windows. (e.g. http://www.primopdf.com/) So the addition of pdf support in FM8 is pretty anti-climactic anyway, and its loss in runtimes even more so. Although, I agree with you that it *is* annoying. -regards, Dave |
#8
| |||
| |||
|
|
That said, Mac's can create PDFs from any print job, and you can get free software to do same for windows. (e.g. http://www.primopdf.com/) So the addition of pdf support in FM8 is pretty anti-climactic anyway, and its loss in runtimes even more so. Although, I agree with you that it *is* annoying. Dave |
|
Though it's annoying, it seems FMI didn't have much choice on it. They are likely licensing the technology and it's hard to license on a per-user basis when you don't know who the runtimes are going to. [Howard] |
|
A runtime solution should be fully self-contained. My clients will not want to install extra (PDF) printer drivers in Windows and, in any case, I will not be able to script FM to cover all of the permutations. I simply want a button that will export a report to PDF. I have users with Mac and Windows and checked I could create Windows runtime solutions with FM8 Advanced (running in XP under Virtual PC for OS X) before I made the move from MS Access to FM8. I had powerful programming/debugging capabilities in MS Access (and the unrelated DOS Open Access - circa 1985 - for that matter). They also both use industry standard SQL relational database management. I waited for FM to get a minimum of these capabilities before making the move. For me the main attractions of FM8 are its friendly user interface (although this takes a considerable amount of background effort to make bullet-proof), cross-platform capabilities and self-contained runtime applications. In my circumstances the inability to export a report layout to PDF is a serious limitation and I hope it is fixed in a future update. Michael Paine 42 wrote: In article <436bd0e9$0$22880$afc38c87 (AT) news (DOT) optusnet.com.au>, mpaine (AT) tpgi (DOT) com.au says... Page 90 of my FM8 Advanced Developer Guide lists the script steps that are IGNORED by the runtime application. The list includes "Save records as PDF" ! As it turns out, this is going to be a nuisance for me as I am currently working on a layout that uses container fields to create a colour-coded diagram (actually crash test dummies). I have already successfully exported a trial result as a PDF. I was intending to have this feature in a runtime version but Ian's experience suggests this will not be possible. This is a serious limitation to runtime applications and makes Advanced version less attractive for developers. Not really. Beleive it or not most users of Advanced are in it for the script debugging, custom functions, etc... not for runtimes. That said, Mac's can create PDFs from any print job, and you can get free software to do same for windows. (e.g. http://www.primopdf.com/) So the addition of pdf support in FM8 is pretty anti-climactic anyway, and its loss in runtimes even more so. Although, I agree with you that it *is* annoying. -regards, Dave |
#9
| |||
| |||
|
|
A runtime solution should be fully self-contained. My clients will not want to install extra (PDF) printer drivers in Windows and, in any case, I will not be able to script FM to cover all of the permutations. I simply want a button that will export a report to PDF. |


|
I have users with Mac and Windows and checked I could create Windows runtime solutions with FM8 Advanced (running in XP under Virtual PC for OS X) before I made the move from MS Access to FM8. I had powerful programming/debugging capabilities in MS Access (and the unrelated DOS Open Access - circa 1985 - for that matter). They also both use industry standard SQL relational database management. I waited for FM to get a minimum of these capabilities before making the move. For me the main attractions of FM8 are its friendly user interface (although this takes a considerable amount of background effort to make bullet-proof), cross-platform capabilities and self-contained runtime applications. In my circumstances the inability to export a report layout to PDF is a serious limitation and I hope it is fixed in a future update. |
#10
| |||
| |||
|
|
In article <436bfbeb$0$30573$afc38c87 (AT) news (DOT) optusnet.com.au>, mpaine (AT) tpgi (DOT) com.au says... A runtime solution should be fully self-contained. My clients will not want to install extra (PDF) printer drivers in Windows and, in any case, I will not be able to script FM to cover all of the permutations. I simply want a button that will export a report to PDF. Yes I get it. Given how many applications out there support direct PDF output, and their long history of doing so -- this is a serious problem; users have come to expect this functionality built into their applications ... er... wait... um... outside of Adobe products how many mainstream apps do this? ![]() FWIW, yeah, PDF creation *is* catching on in the mainstream, and yes, the next version of Office will have it, and so on. FM8 really is on the front end of the pack on this though, there really aren't many apps shipping with native pdf support yet. I'm sure we'll see better PDF support and pdf support in runtimes eventually. In the meantime, since the free pdf drivers aren't adequate -- you could always license a PDF plug-in for filemaker -- there are a few of them around; and have been since at least version 5, long before FM offered anything looking like pdf support in any of their products. google: filemaker pdf plugin click "I'm feeling lucky" They even license it for runtimes. ![]() I have users with Mac and Windows and checked I could create Windows runtime solutions with FM8 Advanced (running in XP under Virtual PC for OS X) before I made the move from MS Access to FM8. I had powerful programming/debugging capabilities in MS Access (and the unrelated DOS Open Access - circa 1985 - for that matter). They also both use industry standard SQL relational database management. I waited for FM to get a minimum of these capabilities before making the move. For me the main attractions of FM8 are its friendly user interface (although this takes a considerable amount of background effort to make bullet-proof), cross-platform capabilities and self-contained runtime applications. In my circumstances the inability to export a report layout to PDF is a serious limitation and I hope it is fixed in a future update. You lost me... its not like Access or DOS Open Access have ever included that feature. Don't get me wrong, I agree its annoying that its ommited in the runtimes. I'd like to see it there too, and don't think there is a satisfactory reason for its absence. I think it will eventually be available. And I fully support your 'cause'... I want PDF support in runtimes... I want BETTER PDF support from FileMaker period. |
![]() |
| Thread Tools | |
| Display Modes | |
| |