Using CVI 8.0.1, I am successful at using NI-Reports to generate a .PDF output to an Acrobat distiller printer. What I would like to do is to pass a .PDF file path name to Acrobat so that it will use it for saving the output to this specific destination. What are the approaches to doing this? Any examples?
For future reference, are there other nifty alternatives toward generating .PDF output files besides using Acrobat?
Yes, I want to save it to a file. Refering to paragraph 9 in the link you provided above, when the popup occurs asking for a filename to use, I want my CVI program to the specific default file path and name to the popup. How can CVI pass this file path?
Unfortunately, there is no way to specify the file path for that dialog using the NI-Reports API. NI-Reports was not developed with printing to files in mind, so the solution discussed in the knowledge base should only be considered a work-around at best.
Thankyou for your suggestion on using GhostScript to produce a PDF file with forward file output naming directives (and perhaps much more). It is still not clear how I associate GhostScript with an NI-Reports handle? Or do I abandon NI-Reports altogether and use the GhostScript .DLL to generate reports in a GhostScript environment? Please explain further...
You cannot associate your NI-Reports handle with GhostScript. You should be able to use GhostScript with CVI, but there is no built in functionality to do so.
Thankyou all for your comments. I did more investigation with Sheetal's earlier suggestion and got it to work. I am able to send an NI-Report generation to a PDF printer and build a PDF file, then subsequently view the .PDF file upon demand. What's more, I can programmatically specify the path and file name of this file within my CVI program. With just a few more features that could hopefully someday be supported by NI-Reports (or a tool-kit) then this adds another powerful tool to CVI.
It would be nice if NI would take the extra step to build prgrammable document saving functionality into the NI Report library. I found NI Report fairly easy to use but when it comes down to saving the document, I find the workaround a less desirable solution. It should be a programmable solution not a workaround. Hopefully, NI will take the hint after and take the extra step.