I'm using the latest version FoxBin2Prg v1.19.42.
When using the convertion from text to binary file (prg2bin) with an external command, errors are not returned properly to the calling command.
You can reproduce the error by downloading the attached file "_errorreport.zip", unpacking it and running the batch script runfoxbin2prg.cmd.
The third test (subdirectory test3) tries to compile the text version of a simple form and fails.
Comments: ** Comment from web user: fdbozzo **
Ok, I think I've found the problem, and seems related to DOS or VFP (not sure who of the 2) when the parameters begin with "-" and are received from an external program.
Just in case you want to force FoxBin to generate an error using any normal file, in this same version I've added some testing code to do it. Just add "SIMERR_I1" in the cType 2nd parameters, so your call could be something like this:
The keyword SIMERR_I1 simulates an error (with ERROR command) on the input file, to let FoxBin think it have an error and force it to return the error code 1 to calling program:
```
call foxbin2prg.exe test3\f_test.scx BIN2PRG-SIMERR_I1 0 0 1 1 1
```
(Note that BIN2PRG does not begin with "-" this time)
Once you have tested that you get the respective error code "1", you could use the normal parameter without the SIMERR keyword:
```
call foxbin2prg.exe test3\f_test.scx BIN2PRG-SIMERR_I1 0 0 1 1 1
```
Let me know if this solves the problem.