Russell,

I've never used printing (locally) under terminal services.
But when I do it on my LAN, to a printer on some other machine, the machine with the printer attached sure appears to SPOOL it prior to printing.

Assuming so, I'd **guess** the same would hold true for a TS print job printed on the locally attached printer.

good luck


>Thanks for the reply, Neil. I was a little unclear on #4. You say "on that workstation," but this is Terminal Services . . .
>
>>Hi,
>>Check the following:-
>>
>>1. check for printer info in the report
>>2. check that the printer doesn't have spooling disabled
>>3. Upgrade or Downgrade the printer driver. Is it a TS compatible printer?
>>4. Is the spooler corrupt on that workstation.
>>
>>>I have a client that is experiencing an error 1957 when printing a report in a program running under Terminal Services. 1957 is "Error accessing printer spooler." Here's the code that's being executed:
>>>
>>>

>>>TRY
>>>   SET PRINTER TO NAME (PrinterName)
>>>CATCH
>>>   SET PRINTER TO NAME GETPRINTER()
>>>ENDTRY
>>>

>>>
>>>Prior to this code I've used the GETPRINTER function to let the user select a printer and I'm storing it in the PrinterName variable. Originally, there was no TRY..CATCH code. What I did was add that code so that if the first SET PRINTER command threw an error, I could try a different approach and put the call to GETPRINTER right in the SET PRINTER command. Strangely, this fixed the problem, but I try to clean up afterwards and reset the printer to what was originally selected. Unfortunately, that code (SET PRINTER TO (OrigPrinter)) is sometimes throwing an error. I haven't been able to recreate this, but the users are definitely getting it. Anyone know of an issue such as this with VFP under Terminal Services? It's intermittent and may be related to specific user accounts.
>>>
>>>Russell Campbell