>>Mat,
>>What OS are you using as the client? By any chance is it Win9X? If so, you may have a problem using this technique with printer share names that are longer than 8.3 or have embedded spaces. You might try changing the share name.
>>
>
>Larry,
>
>I am running NT Server 4.0 and NT Workstation 4.0. My shared printer was named Network IIIp, but I changed it to HP3p and now it works! Thanks for the great suggestion.

I tested this after I posted on my home network with NT Server/NT Server and found the same thing so I guess its not a limitation of the OS.

>
>Does this present a problem for me in distributing the application? It was easy for me to change the share name in my test environment, but would you handle this at client sites? Is this a limitation of the CopyFile API and is there another alternative to get around it?

This may be a limitation of CopyFile and embedded spaces only. Try surrounding the printer name with quotes. This was the way to get around it when using the Command prompt in the Dos/Win9X days.

HTH.