>Hi Sergey,
>
>I tried to do it as follows:
>
>SET PRINTER TO NAME "Generic / Text Only"
>REPORT FORM &rapnavn NOCONSOLE TO FILE &lcFileName ASCII NOOPTIMIZE
>
>And Also...
>_ASCIICOLS=105 && Landscape width
>_ASCIIROWS=48 && Landscape height
>SET PRINTER TO NAME "Generic / Text Only"
>REPORT FORM &rapnavn NOCONSOLE TO FILE &lcFileName ASCII NOOPTIMIZE
>
>However, Neither has any effect (well the _ASII stuff has an effect but
>there is always data still missing...)
>
>DO you have any other ideas on this?
>
>Does anyone know if the ASCII bug on REPORT FORM is fixed in VFP8?

This problem also exists in VFP 8.
I think that this is not listed in VFP bug lists and is not recognized as
bug in MS.

Some ideas:

1. You can use the free report manager at

http://sourceforge.net/projects/reportman/

It can access dbf files only using ODBC.
However, since it is open-source, you can add a native dbf support to it.

2. In you application create a test report and calculate the number of lines
which must appear in report.

Before generating text file, try run test report against all installed printers in user and count the number of lines in result file.
If you find some correct pritner driver, you may hope that this works
with your actual data also.

Data courruption only causes line truncation.
You can determine the mumber of lines in a result file by using some arithmetics. After that you can check the number of lines in result text file
to dedect data corruption.

3. Modify frx file before generating txt file programmatically:
Add an lot of emply space before and after each row.
Having a lot of empty space decreases the loss on data.
Remove empty lines from result text file programmatically.