Just an FYI, talked to them, and they don't have an update that will read the binary stuff that is stored in the VCX which is specific to the control. :(

Bob

>That's why I said talk with David; in other conversations, I recall him having said something about saving properties in the version under development.
>
>>From the docs on the website, it only saves them if the properties were set on the VFP property sheet. This is not possible with some of the more sophisicated objects, like activebar, etc. By the time I've reset all the properties from the right click custom property manager to VFP I can propably rebuild the class from scratch...
>>
>>Bob
>>
>>>Check with David; I believe his current version does that.
>>>
>>>>>>Has anyone upgraded a dbi-tech component? I'm planning on upgrading the ctlist component that I have subclassed in a VCX.
>>>>>>
>>>>>>Here's the problem. It seems as if I have to define the class all over, with all of the properties, etc. from scratch. Is there any way you can plug in the new component?
>>>>>>
>>>>>>When I copy the ctlist.ocx into my \system32 folder (where the previous component resided), when I try to open the Class in the designer, it can't find the component. Its oleClass of ctLIST.ctListCtrl.1 has been changed to ctLIST.ctListCtrl.5 in the new control. I've tried hacking the classlib but can't find these properties where I could try changing it manually.
>>>>>
>>>>>Bob,
>>>>>
>>>>>Check OLE Fixer File #21566
>>>>
>>>>THANK YOU! I investigated this product, and unfortunately it can't save the "properties" you've set on the previous version.. :( (with some controls you set a lot of properties so this doesn't save you any work on the upgrade.
>>>>
>>>>Bob