>>Can anyone tell me the way to do it.
>>Has anyone re-written the report converter to help them.
>>Is there a 'magic' font out there that matches the DOS one exactly.
>>Does VFP6.0 convert them any better?
>>
>>I am willing to try anything (legal!)
>
>Did you try to use them unconverted? Without trying to open them in the report designer. VFP runs them just the same, and it will probably use Courier fonr or FoxFont. There seems to be some way of setting a font globally for printing DOS reports, for compatibility with FPW or something - ah, here it is:
>
>[quote from help]
>SET PRINTER FONT
>
>FONT cFontName [, cFontSize] Specifies a default font for printer output. cFontName specifies the name of the font, and cFontSize specifies the point size. For example, the following command specifies 16-point Courier font as the default printer font:
>
>SET PRINTER FONT 'Courier', 16
>
>If the font you specify is not available, a font with similar font characteristics is substituted.
>
>[end quote]

Hi,

Due to past circumstances we cannot use them unconverted. In the old version, the system opened 40 dbfs. When users tried to run 2 copies, they ran out of file handles - as did the WIN95 servers. To be clever we open 0 files. When the program required a file, the alias was not found and the error trapping opened the required file for us. The max ever opened at one time was then 15 - much better. This was by far the easiest way to get around the problem.

Now, in VFP, the error trapping does not trigger when in a report. This stops the files from being opened. We have now converted them and placed the required files in the data environment.

If only we could use the unconveted reports.

Any other ideas.

Regards,

Kev