>>See my reply to Paul - in all probability, the old version of the control does not have the same CLSID as the new version, so they are not programamtically and functionally identical, in the same way that two different versions of ListView or TreeView would be the same.
>
>>If the two versions share a common VersionIndependentProgID, and you instantiated the control programmatically using the VersionIndependentProgID rather than through the Visual form interface, there would be workarounds, but unless the interfaces are indetical, or you do something programmatically to bind the control late through the VersionIndependentProgid, you're stuck either readding it, or writing code to hack the SCX, which is no better, and no help if you've already deployed the SCX compiled into .EXE
>
>This still does not explain why I could recompile the ocx and continue using it in VFP without further ado a few months ago, and now I cannot any more? As far as I recall, it started when someone decided the ocx could have a more meaningful name.He also made some minor changes then.
>

You changed the interface. that's why. Early binding breaks when an interface changes.