I'm looking for a free FRX TO PDF converter but CutePDF doesn't work well as it always asks the path & filename to save as is really a pain. I've seen others but the Acrobat PS Driver is non existant for win7 x64.
I pre-configure BullZip so that all PDF writes to go out to the same Directory & Filename. Allowing for 'blind' over-writes, etc.
Then after a PDF write within my VFP code I can 'know' where to find the output PDF file which I can then move to wherever I need and rename to its intended filename along the way COPY FILE <orig> TO <new>
XFRX is not free, but it's not very expensive either. It's the most flexible tool of its kind I've come across, and only needs about three lines of code to ouptut a PDF to any filename and directory you choose.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
And those dependencies which control the Default settings, can, as I said above, be have their final values easily changed dynamically by the VFP application after the PDF write has completed.
It has worked for one of my clients to send out 200+ PDF files each day as email attachments, all with unique filenames and locations.
If you want some more comprehensive PDF driver which will allow you to dynamically pass it filename parameters, etc., then expect to pull out the credit card.
If this is a Business Critical operation quit trying to 'low-ball' it, you get what you pay for.
Is there a way to use FoxyPreviewer within VFP8 ?
FoxyPreviewer looks greats, can traslate to pdf, xls, etc and is easy to use.
I have only VFP8 and need only reports FRX to Xls (no to-Pdf necesary)
Well to export data to xls, EXPORT Type XLS or COPY TO TYPE XLS surely are more natural ways. And if you need xlsx, there are adodb providers for creating excel sheets. Besides you can always make use of OLE automation.
If you want a report layout, I question usage of xls, excel is a spreadsheet application - the german term, retranslated, "table calculation" suggests even more, it's not meant for reporting, but for calculating with data in it's table cells.
If that is acutally the reason you want to export to xls, then ole automation is much better for that matter than using frxes.
With an frx as the basis of an xls, even if xfrx supports that, you will not have much control about which columns your frx detail band fields will go, also I doubt formulas for summation, etc, which you may use via report variables, are not automatically converted to cell formulas in the resulting excel spreadsheet, the conversion rather is visually than functionally.
OLE automation of excel will yield the better results here, you are in charge and control how the excel sheet is created including the visual layout and formulas in it.
And if you intend to use xls for data transfer, it's even more questionable to go through a report.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.