Ok, it was just a guess.
I just remember, some years ago, that I had a situation where some of the workstations in the building had the same printer mapped with a different name than my computer did, and it caused this to happen. I think I might have renamed the printers on my computer to make them easier to distinguish. Of course, this was VFP3 and Win95.


Bill

>If a print queue is defined on the Citrix server to print to a network printer (NOT a client printer), the name is not altered in any way. It is no different that a newtwork printer definition on any version of NT. Only client printers have names like "HP... on < client name >" A straight network printer in Citrix or other Windows OS always says "< driver > on < server >" unless it prints through a local port (which can be a print server like JetDirect).
>
> Randy
>>
>>I think that this is the trick to get it to not print to a specific printer, but to the users default printer. It did remind me of how the printer is specified in a fox report though. It stores the printer name from the developers machine in the fields specified above. If the name does not match (even the same printer) on the client machine, it will just use the client default. It may be that Citrix renames the network printer to something like "HP... on ..." like it does for drives and local printers. That would cause the printer name to not match and the default printer to be invoked.