If the CLSID have not changed between the versions (this should be true at least for 93th and 100th versions) there should be (as you have said) another reason. This could be:
1. a missed type library registration, or
2. type library that is registered with differen CLSID or
3. the Type library is registered on a different file-path location from the one TLB file is located (this assumes that the type-library is external file)
4. Not comptible interface definitions. For example the interface that is used by the 98th version is not compatible with these ones used in 93th or 100th version.
5. other incompatibilities between the control versions.

I cannot figure it out, not having at least 93th, 100th and other version (incomatible) of the ActiveX control in question to play with. I can only make suggestions based on my experience with ActiveX controls in VFP.

Best Regards

>Zlatin,
>Thanks for providing some insights on how to fix the problem. In my case there is probably something else which makes the form behave strangely. CLSID hasn't changed between versions , plus as I mentioned I can open the form with version 100 after rolling back to version 93.
>
>Michael
>
< snip >
>>> My question is what may cause such a behaviour :
>>>1. Something strange in .scx/sct files ( if so where to search )
>>>2. Control creators missed something which is required when new version is released.
>>>3. We should expect such a behaviour with Foxpro forms and I need to include control again from toolbar and then paste methods saved in advance.
>>>
< snip >