Hi,
In addition to what Sergey recommended.
If you have the printer driver installed on the client and it isn't on the Server you will get the error.
The same driver has to be installed on the Server, Win2003 tries to match the drivers, but if it can't it will error.

>I don't know if this is the right forum but here we go:
>
>I’m testing out a VFP 6.0 application on a server environment using terminal services on Windows Server 2003.
>
>We are running into an interesting problem.
>
>When I try to print a report on a local printer through VFP app, it works fine as long as the printer drivers are already installed on windows server 2003 ( in other words they have to be part of the installation of W2K3).
>
>I have a HP Laserjet 1100 and a HP LaserJet 6. I can print fine to those since drivers are included in W2K3.
>
>If I try to print to a fallback driver (which is a generic driver that most printers will print from), or try to print to a driver that I installed for a specific printer, the VFP app. throws an error.
>
>Error # 1958 – error loading printer driver.
>
>The detail on that error states: An internal call to the LoadLibrary( ) function has failed. Visual FoxPro calls this function through either PRTINFO( ) or SET PRINTER TO.
>
>This is definitely a Visual FoxPro issue. When I try to print using Wordpad, I can print to any of the printers fine.
>
>I select a report then click the print button. It lets me select a printer from the list after which it throws the error.
>
>The Set Printer To commands related to this report have been removed.
>
>Any ideas on what the problem might be?
>
>Marcel