>>Fernando, first of all, congratulations for your FoxBin2Prg latest announcement.
>>
>>Taking up from your advice to Dmitry, let me present to you a similar situation for which I was considering using FoxBin2Prg as you just stated. But with a twist.
>>
>>I have a bunch of classes incorporating an ActiveX control that I recently upgraded from CLSID x to CLSID y. I looked into the FoxBin2Prg generated code for the library, saw the path to the OCX that could be easily edited, but also a binary information segment that I wouldn't know how to handle. Also, the CLSID is not in sight.
>>
>>Is there a simple answer to "is it safe to remove the binary info in the value attribute"?
>>
>>END OBJECT: BaseClass="olecontrol" OLEObject="path to ocx" Value="base64encodeddata="
>
>Hi Antonio! Glad to read you :)
>
>You can't take out the OLE encoded data, because then the error "OLE error code 0x80030050: Unknown code status code. OLE is being ignored. Record number XX" is thrown.
>
>About modifying the binary data, Idon't know in which part of the BLOB is the info stored, and it's not safe to touch it.
>
>One thing you can do (and may work) is saving the new control on a new test-form (or class), exporting to text and copying the entire "END OBJECT" line to replace in the original file, so you preserve all the other properties, but I didn't test it.

Good advice, Fernando. I'll try it and report back to you (eventually, it may be useful for the FoxBin2Prg knowledge base).