I have to execute DOS-commands from within a Windev-program.
This works (fine) since a longer while using an earlier filled-in
(MS-)Batch-file and then asking Windev to execute that Batch-file
via the statement ExeRun.
Ex: ExeRun("My_BatchFile.bat",,exeActif,exeBloquant)
Within the My_Batch-file.bat there is most of the time just one command:
copy c:\labels\out.asc LPT1:
Sometimes a few more lines like (when printing to a Serial-printer):
mode com2: 9600,n,8,1
mode lpt1=com2
copy c:\vblabels\out.asc LPT1:
As said before, this solution via the Batch-file "works fine",
but is a bit ugly, as, each time, it executes,
it shows for a split-second the "black" MS-Dos-screen.
I tried several ways already to write a "straight" ExeRun-statement like:
lbPrintRes = ExeRun(lsDOSCmmnds + "copy c:\vblabels\out.asc LPT1:",...
exeActif,exeBloquant)
Where lsDOSCmmnds = "C:\WINNT\SYSTEM32\cmd.exe "
But lbPrintRes always returns False!
For the Serial example I manage to execute the "mode"-commands
(still with a black-screen,) stating:
lbPrintRes = ExeRun(WinNTSysMap+"mode.com com1: 9600,n,8,1" ,...
exeActif,exeBloquant)
lbPrintRes = ExeRun(WinNTSysMap+"mode.com lpt1=com1" ,...
exeActif,exeBloquant)
Where WinNTSysMap = "C:\WINNT\SYSTEM32"
But then again I cannot send the following "copy"-command
from within Windev via an ExeRun(...)
Anybody knowa more about this?
Thanks foor Your attention, help.
Lieven De Nys.
Member of the Benelux (Dutch speaking) Windev-Developpersgroup.