>>In any case, this stupid report doesn't work! I spent ~3 full days working on this report and the problem is, that I need output to ASCII file. Print Preview works great, Print also works, but ASCII file produces something weird (truncated strings, etc.). May be we have to find another solution here. Really pity, that I already spent so much time on it :((((
>
>Usually what you have to do to get an "improved" ascii report is make sure your fields are actually wider than you think they need to be (on the report, not in the tables) and to make sure you don't have any extra space at the bottom of the band, between the fields and the band. Seems to me I remeber something about a KB article and setting the ASCIIROWS to 30 or something like that. And you're right, there are no commas when you leave the space out, either.

Hi Fred,

Seems I found a work aroud this problem, but before I'll take this route, I want to ask this question (I'll start a new thread also):

Is it possible to insert an ASCII characters in VFP report writer, particulary, CHR(9) (Tab) The program, which works with this output file expects a Tab at some place, then it knows, what to do with it.
As a work around I can think off, is to create a report with, say, tilda, then ran a special program, which would replace tilda ~ with chr(9). This would work, but I just want to ask you, if it could be done in Report Writer directly?

Thanks a lot in advance.