Jim,

Thanks for your reply.

This is a good idea, but the problem I have is related to the way output is currently produced. We have a lot of complex legacy reports that produce plain text output. These reports are generated with procedural code. A typical report may look like this:

WITH This

   SCAN

      IF IsNewGroup
         
         *-- new Group Company
         .LineSeparator()
         .GroupCompanyHeader()
         
         IF .GroupCompanyPaymentDetails() > 0
            .GroupCompanyPaymentFooter()
         ENDIF
         
         IF .GroupCompanyReceiptDetails() > 0
            .GroupCompanyReceiptFooter()
         ENDIF
         
         .GroupCompanyNetPosition()
         
         IF llGC
            .CompanyCurrencyOffer()
            .GroupCompanySettlement()
         ELSE
            .VendorSettlement()
         ENDIF
      ENDIF

   ENDSCAN

   *-- write payment summary
   .LineSeparator()
   .PaymentSummaryHeader()
   .PaymentSummaryDetails()
   .PaymentSummaryFooter()

   *-- write footer
   .LineSeparator()
   .ReportFooter()

ENDWITH

Each of these methods may query data from different sources and process 0-n records and then write the data to the output file. This is done within a single method (This.Write() ). Therefore, the easiest way would be to substitute the WRITE method with a call to some HTML class that would receive the data and write the formatted HTML code to a file.

This is the main reason why FRX or template based solutions are not really suitable in this situation.

BTW, I've looked at your eReports and really liked it!

>Daniel,
>
>There are several ways to output to HTML. One of the easiest ways IMO is creating your template HTML output, so you have the design look and feel, then use VFP's text merging capabilities.
>
>Jim Eddins
>
>>Hi,
>>
>>I've been looking at different reporting tools for VFP. I looked at XFRX, Frx2Any, eReports, MindsEye Report Engine, etc. These are all great tools, but they are all FRX based.
>>
>>I am looking for a solution that allows me to output HTML code without an FRX. This is because we have some special reports that would be rather difficult to implement with an FRX.
>>
>>The closest tool that I found for our requirements is webReporter from Mark Wilson (from his FoxTalk article from August 2000 http://www.pinnaclepublishing.com/foxtalk/FTMag.nsf/WebIndexByIssue/5C32118E1182D02A8525692E007B1EB9?opendocument
>>). It's very easy to use, yet flexible. Before I start using this class and adding new features I was wondering if anyone here has used webReporter and maybe added some enhancements. If yes, care to share them?
>>
>>Thanks in advance.