Thomas,

I have done many reports to email via PDF format (using XFRX) and it works. But this specific feature (I believe) will work better if the recipient will see the report right in the body of the email. As I mentioned, 99% of the cases, this report will have no more than 10 lines. So it would be easier for a recipient to see the information right in the body of the email.

As far as JSON and "mirroring V-VM scenarios", I don't know these technologies. So I will stick with what I know.

Thank you!


>Dmitry,
>
>on first reading only had the STRONG urge to make you rethink enabling HTML report output.
>Wondering on my strong hunch, I guess for me the dichtomic PDF / Ascii table is valid for a lot of scenarios,
>but HTML is not that unusual this millenium.
>
>After mulling a bit : I STILL think I'd discuss the benefit/ (continuing&future!) effort ratio for such a task a bit more.
>BUT: large part of quesy feeling comes from planned way of creating output via tool like xfrx.
>
>If your angle is the "paper similar" output, stay with PDF and ASCII. If HTML really is necessary,
>do it right: just create a data set in JSON and define HTML reports for that, mirroring V-VM scenarios of best practice in GUI design.
>Viewing on mobile will be next issue, and doing refinements via vfp report might become too Goldbergian
>
>my 0.02€
>
>thomas
>
>>Hi,
>>
>>I need to add a feature that will email a relatively small report (no more than 2 pages) and I prefer to embed the report into the body section of the email. Therefore, the report has to be converted to HTML file. Are they tools in VFP that would allow this task?
>>
>>I have an older (a couple of years old) version of XFRX which I use to convert reports to PDF. It could be that XFRX has an option to convert to HTML too (I have to check that).
>>
>>Any other suggestions would be appreciated.