>>>>>A client has a printer with three input bins connected to a networked print server (not attached to a computer).
>>>>>For example, the 3 'names' that appear in his W2000 or XP PRO printers are 'invoices', 'packing slip' and 'shipping labels'.
>>>>>These are the names that appear in a right click and as a result they can be renamed.
>>>>>Also, if we look deeper into the properties of these three printers the IP address is 192.168.1.100.
>>>>>Would the syntax of the SET PRINTER TO NAME be '\\packing slip' or '\\192.168.1.100\packing slip' or something different?
>>>>
>>>>If the local printer name is e.g. "packing slip" then shouldn't it be

SET PRINTER TO NAME "packing slip"

>>>I realized after I sent the message that it is in the wrong forum - sorry.
>>>From the help (VFP 6) it appears that you need a server name and printer name.
>>>Am I missing something?
>>
>>I have a printer named "HP Laserjet 5P" on my local machine. Running

SET PRINTER TO NAME "HP Laserjet 5P"

works fine. I think you need to prepend the server name only if the print queue is not on the local machine.
>
>That was my point.
>I am referring to 3 bins on a HP that is on a print server that is not connected to a physical workstation.

My point is that Windows, when set up properly, takes care of all the low-level details like that for you. From what you said earlier I assume the users have 3 virtual "installed printers" named 'invoices', 'packing slip' and 'shipping labels'. IOW a user can go into MS Word, create a document and in the Print dialog choose to print to the 'invoices' printer, in which case the document will be printed on that printer on paper pulled from the 'invoices' bin.

Sure, under the hood that means knowing which IP the print server is on, which port of the print server the printer is attached to and the initialization string that must be sent before each job so that the correct bin is selected. All this has already been done for you in the setup of the network print server and the settings of the "virtual" printer that's been installed at the workstation. One of Windows' nice features is the ability to abstract hardware in this fashion to make management easier.

So if everything is as you've told us so far, just print to any virtual printer as if it was a real, locally attached one. Windows and the network print server will take care of the rest.