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 **
Hi Ralf:
The main reason for not generating the text version when found duplicated controls, is because the affected code is not only the control, but other areas too. In example, when a duplicated control is detected, the same record of the scx/vcx have info about properties, protected/hidden names of properties and names and all the methods associated with the control found. Looking on the text for all of this (distributed in various areas of the header and body of the text file) is far more difficult than opening the form/class as a table, looking which of the duplicated records is the good one and deleting the other, which eliminates all the related info at once and is safer too.
When deleting the control in the text file (the ADD OBJECT) you can left, whithout knowing it, various properties and method definitions orphaned and many times duplicated with the same of the good control. I've seen this scenario many times because at the beginning I did the same you do :) ...until I've found the orphaned properties/methods and duplicated too.
Even when only duplicated methods are found, the only way you have to know which one is the one it is executed (the good one), is opening the form/class method in the VFP IDE and looking for something (a block of code, a comment or something special) that can identify it, so when you next open it as a table and look for the duplicates, you keep the record that have this special identified code/comment/etc you saw on the IDE and delete the rest of duplicates.
Regards,
Fernando.-