>>>>>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.
>>
>>Thanks Dragan
>>
>>My DOS is a bit rusty. I undertand "!@net use lpt1>prn.txt" will "pipe" the output to file prn.txt, but when I run the command, from VFP command window, I get a DOS window flash up for a split-second and then I can find the file nowhere.
>
>Well then instead of prn.txt, put a fullpath of a file, surround with quotation marks as needed.

I have done that already - not a sausage.

>Also, get Ed Rauh's Api_AppRun and use that to run it invisibly - if it's from VFP.

I no naaaarssing of zees. Anyway, it's most definitely a FPD exe.

>
>In FPD, I think we used a Save Screen or something like that for such cases - the screen would scroll briefly and come back immediately after. The best we could do then.