I have an application written in dbase IV, which runs fine in Windows 98.
I RUN a batch file to use 3rd party print software, called with RUN chargfcl.bat
I tried @echo off in the batch file but that did change anything.
The batch file contains a single line like c:\printexp\vlrepprn.exe c:\printexp\chargfcl.dtt
When the batch file runs the following occurs.
1. The batch file executes correctly and the new window is created and displayed. But the batch file hangs until I close the called application. In Windows 98 I can call multiple batch files only limited by memory, and dbase is active when I return to it.
2. The Dbase Screen is compresses to the top half the screen. The bottom half is Black, but displays the echo of the batch command immediately under the Dbase part of the screen.
The typical Dbase display should be a full screen menu, which now gets squeezed to half its normal size.
I am not too fussed by #1 because I can instruct the user to print then close.
#2 is embarrassing and looks bad.
NOTE every thing runs OK in Win 98.
Any clues?
I RUN a batch file to use 3rd party print software, called with RUN chargfcl.bat
I tried @echo off in the batch file but that did change anything.
The batch file contains a single line like c:\printexp\vlrepprn.exe c:\printexp\chargfcl.dtt
When the batch file runs the following occurs.
1. The batch file executes correctly and the new window is created and displayed. But the batch file hangs until I close the called application. In Windows 98 I can call multiple batch files only limited by memory, and dbase is active when I return to it.
2. The Dbase Screen is compresses to the top half the screen. The bottom half is Black, but displays the echo of the batch command immediately under the Dbase part of the screen.
The typical Dbase display should be a full screen menu, which now gets squeezed to half its normal size.
I am not too fussed by #1 because I can instruct the user to print then close.
#2 is embarrassing and looks bad.
NOTE every thing runs OK in Win 98.
Any clues?