>>If you dont want the user to change the .bat, use your .exe to do the job (provide some interface and recreate the .bat)
>
>Ah, I see now what you mean. Maybe a good idea. Trouble is, it still needs some knowledge by the user, in providing the network connexion and printer share name, eh?
>
>Hmmm, I must smoke on this.

Basically, roll your own. FPD2.6 has textmerge, so you can generate the .bat file for each WS - and you can have a table of printer assignments, i.e. which WS uses which printer. Just check for the .bat file (or do a !@net use lpt1>prn.txt and read what it says, and regenerate the .bat file if needed). Then just run the .bat file if WS doesn't seem to have assigned the proper printer to lpt1.