Al

Thanks for the reply. I found the answer in the MS Knowledge Base. It is a BUG in VFP. "Printing to a Non-Default printer may cause an error, generate a PDF, quit or print to the wrong printer."

See this page "http://support.microsoft.com/support/kb/articles/Q253/8/84.ASP?LN=EN-US&SD=gn&FR=0&qry=windows%202000%20report&rnk=86&src=DHCS_MSPSS_gn_SRCH&SPR=FOX".

The next question is "How do I find out if this is this fixed in VFP 7.0?"




>>I am using the following command in an app to preview and then print a report.
>>
>>REPORT FORM Myreport.frx TO PRINTER PROMPT NOCONSOLE PREVIEW
>>
>>The app is a VFP 6.0 SP 5 EXE. Everthing works great on Win 9x and Win NT machines. However, we are starting to install the app on Win 2000 machines and running into strange problems.
>>
>>When a user has the Default printer set to a Network Printer they can print to the Network printer or a local printer with no problem. Some users, however, can not get the report to print on the Local printer, it goes to the Network Printer even if they select the Local printer.
>>
>>When a user has the Default printer set to a Local Printer they can print to the Local printer with no problem. But, if they try to print to a Network printer VFP fires off "Error # 1958 : Error loading printer driver".
>>
>>Has anybody seen this behavior on Win 2000? Is it a Win 2000 problem or a VFP problem or both?
>
>The users may have LPT1: redirected to the network print queue by running a NET USE LPT1 \\MachineName\QueueName. This may have been done to support network printing from DOS apps.
>
>Running NET USE LPT1: /DEL will reverse this.