>TExt files don´t have the same formatting capabilities than the report designer in VFP. AFAIK, there´s no way to make the text files look like the preview

Actually, there is, but you have to give up a great deal of functionality to do it. First, all fonts used in the report must be a uniform instance of a monspaced font - using a proportional font will cause columns to misalign. No font size variation can be used, since a text file has no concept of fonts, and no 'special effects' - underlining, boldfacing, small caps, strikethrough or the like can be supported. Neither can colors. Nor can code pages for foreign language character sets in an unambiguous fashion.

Second, the output must be done either using the TO ASCII clause of the report statement, or the printer must be set to use the Generic/Text Only printer driver. If TO ASCII is used, it's likely that both the _ASCIICOLS (the number of columns in an ASCII file's line length) and _ASCIIROWS (the number of rows per 'page' of an ASCII file) will need to be adjusted - _ASCIICOLS will be used to avoid the cutoff of characters beyond the VFP-defined EOL condition, and _ASCIIROWS will affect both paging and the unneeded insertion of extra line feed characters.

If it's necessary to have these formatting capabilities, you may want to investigate tools to output Adobe Acrobat (.PDF) files or Word documents. There are a number of downloads available here on UT for both; I've used FRX2WORD, which converts the FRX into Word Automation to create formatted documents with a great deal of success - if all your users have Word, it is definitely worth examining.