>I have a client that I'm moving to Terminal Services. It's a 64-bit box running Win2K3 64 bit and the application is done in VFP 9 SP 1. We're having some crashes that seem to be related to printing. As many of us know, printer drives used to sometimes play havoc with VFP, but mostly those problems have been fixed. But in this environment we may be encountering the same problems. The printers in use are HP 2420's. We are using the HP LaserJet 5000 Series PCL 6 driver because - and I'm a little sketchy on this - the native drivers are compatible with Terminal Services, I think. Also, these are USB printers and I believe Terminal Services really wants something hung on LPT1. So you can make these work using a different driver, but this may be the cause of the crashes.
>
>I'm looking for some advice from anyone with experience running a VFP app on Terminal Services and how you get printing to work. The user needs to be able to print to the printer from a desktop app and the app running via Terminal Services. I think this was part of the issue, according to the network guys.
>
>What the user sees is what I call the "grey screen of death" - the entire terminal window is grey, but they can still see the tab at the top that has the server's IP address, the close button, etc. I believe they then have trouble getting that to close and getting logged back in. What I see on the server is a error dialog that say the program experienced an error and had to close and it has the buttons for sending (or not) the error report to Microsoft.

Are the printer(s) attached to the TS, or to the client workstations?

There are lots of resources here: http://ts.veranoest.net/ts_printing.htm

In general, and where available, use drivers that exactly match the hardware, try not to use "compatible" drivers. MS-supplied is usually best, then manufacturer-supplied but WHQL-certified. Try to avoid non-WHQL drivers on a TS box.

PCL6 drivers are usually the buggiest, PCL5e less buggy. I have one client running SAP Business one, which exposes bug(s) in the current HP 4240 PCL6 and 5e drivers. The only way I could work around that problem was to switch to the PostScript (PS) drivers.