Thanks for the reply. I had heard of this before. Is there a way to figure out the current printer on the fly ? Or should I maintain a table with printer names associated to users ?

Ideally, I'd like to KNOW the printer name from NT (native command, fll, etc...) and then build my RUN command accordingly.

Your help is very much appreciated.

Henry

>>Hello,
>>
>>I have an app in Windows that creates reports using DOS-only definitions. This is done to allow preview using MODIFY FILE (and hence search capabilities not possible in a graphical preview). If the user wishes to print a segment of the report, I issue a RUN COPY FOX12CPI.drv+PAGERNG.asc LPT1 >NUL
>>
>>FOX12CPI.drv contains control codes for landscape, 12 cpi, etc...
>>PAGERNG.asc is the text extraction of the pages to be printed.
>>
>>This has worked fine for years until the user switched to Windows NT 4.0
>>
>>Now the RUN COPY doesn't work anymore.
>>
>>I succeeded in getting the PRINT option to play a macro that brings up the File/Print dialog, makes the selections and prints the file. Works great, except.... File/Print is ignored if running an EXE.
>>
>>What I need, simply, is to print an ASCII file (that can contain its printer codes if needed). Note that the file must print in FoxFont (to support graphic lines, french accents and non-proportional spacing).
>>
>>Do you know of a magical way to do this ? and why would File/Print not be supported in runtime ?
>>
>>Your help would be greatly appreciated.
>>
>>Best Regards,
>>
>>Henry Dagher
>
>Actually RUN COPY still works in WinNT, but you should first tell computer where LPT1 located. So you firstly
>RUN Net Use LPT1: \\server\printer /persistent:yes
>and now you can
>RUN COPY filename LPT1