>>>I have an application where the user selects which reports they want and then select an output option: 1. Printer, 2. Screen, 3. File, 4. Fax. Selecting the option is one thing. Programming it is another. I had this all working fine under previous versions of DOS and Windows and previous versions of FoxPro. Now I have clients on VFP and Win95 or VFP and WinNT 4.0 and things aren't working anymore. The problem is that printer settings used to be stored in the WINI.INI file and where easily manipulated with a few freeware utilities. With 95 & NT, these routines don't work any more. Is there an easy way around this?
>
>>Look at the GETPRINTER() and releated functions.
>>
>also look at SET PRINTER TO NAME (but this probably goes under "related commands")
>
>another thing you should know is that win95 and NT4.0 use registry files
>for the printers - however API calles that write the WIN.INI file
>should affect the registry (according to the docs)
>In the worst case you can alwys use the set of API calls
>that work directly with the registry - but IMHO SET PRINTER TO NAME
>should be enough

Arnon

IMHO I would stick to VFP high level functions as much as possible.

Tom