The problem with long reports (I mean from 50 pages on approx) is cost of printing in a laser or ink printer. So a lot of users would want to print them in a dot matrix printer and you have a new problem: time.

For a lot of countries this is not a problem, since most businesses don't have a matrix printer. But in Chile most businesses have one because you need one to print legal invoices (they are reviewed and stamped by the IRS).

When I said that frx2any is slow I did not mean printing time, I meant report generating time, this is why I discarded using it. I checked your classes for generating ASCII and Excel reports and indeed I liked them.
What I finally have is: I like and need the good looking reports in Windows fonts, and I also need the fast printing (and Excel viewable) solution, so ideally I should generate both interfaces, one with the report writer and the other with the aid of you classes. It's going to be double the work, but I don't see another solution.

Best,
Javier.

PD: I saw your address in Bolivia, so I suposed you were proficiency in Spanish (great!)

>Well, yes, the main reason many people create text-files is for speed. I don't know frx2any, but I assume it prints using Windows fonts, not sending text to the printer (that is, in text-mode). The same basic problem exists with the report writer.
>
>To make all the fields fit (assuming you use my text-report download, or create your own solution which prints in text-mode), you have several options:
>

Use 12, 15 or 17 CPI, which is similar to reducing font size.
>

Use a wide-carriage printer (carro ancho), at least for some report.
>

Divide the report into two or more pieces, vertically.
>

Use output to Excel, and show it on screen (my class supports that option, too), or have Excel split the output vertically. (This is a standard option in Excel.) However, once again, you will have the slow printing.
>
>BTW, I speak Spanish too, but I continued the thread in English, since this is a specific request from the UT team (not to change languages within the thread).