>Hi,
>
>I am about in the same situation as Paul Robinshaw, i.e. I have created an activeX control in VB I use in VFP. My problem is slightly different:
>
>At first everything worked fine, but now every time I rebuild the control I have to tell VFP to use that control, and I have to add the controls to my form again, because if I open the form I get the 'class not registered' error message. The same thing if I want to run the application. Running regsrv32 does not help. Fortunately everything is still in test.
>
>Does anyone know what I have done wrong? (As I said, it used to work).

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