>>>That is what we are doing now, but it is a pain because all maintenance has to be done using FoxDOS. I am trying to finish the transition.
>>
>>Sure.
>>
>>>>Or, use some other alternative to generate text files, such as my download #9991.
>>>
>>>If I recall correctly the limitation to your method is that it does not allow visual design, correct? Or is this a different one?
>>
>>'Tis the same one. No visual interface, but a lot of flexibility.
>
>Too bad. You would have been a hero!
>
>>>I would like to find a way to open the FRX file and modify it on the fly just before issuing REPORT FOR TO FILE ASCII in such a way that it creates the ASCII file correctly.
>>
>>Oh, well, you might use the VFP report directly. But I gave up on that one a long time ago, since it is a little tricky to exactly calculate the row and column position. I did it with experimentation. Perhaps you can find out how many pixels or fractions of mm. go into a row, and into a column.
>
>I've found valuable info in the VFP routines that convert FPDos reports to VFP format. Maybe I'll review that once again. Thank you.
>
>Alex

What's the reason you want to save the report to an ASCII file? If it's so you can attach it to an e-mail, you're better off saving it as MDI, HTML or PDF.

Another possibility is to design the report using the generic text printer driver, which I believe is character-based instead of pixel-based.