Hi Hank,

Thanks a lot for your response. It is a bit late since I already went through all properties manually using the Properties for the ocx (e.g. special dialog). So, I had two instances of VFP opened and was switching between windows and trying to match the properties and make the changes. I think I got most of them done and the appearance almost matches now. I found it hard to use these Properties, though, especially for setting fonts and colors.

I am now mostly interested if anyone here is using the latest version of these controls and can give me some feedback.

>1) Instantiate the old version
>2) get the object reference of the control
>3) use amembers() to get the properties, and from them the values, storing the values where you wish (table, text file, whatever). Do a sanity check on the property/value combinations.
>4) open the control in its class for editing (i.e., not running)
>5) use aselobj() to get the object reference of the control
>6) use the stored property/value pairs to set the properties.
>
>There may be some curves along the path. While I've done something like this in the past, it's been over a decade... The basics of it are using amembers() and aselobj().
>
>enjoy,
>
>Hank
>
>>Hi everybody,
>>
>>I'm trying to upgrade ctSchedule control from DBI Controls into the newest version using their trial version to test. We were using a container based class in our form. So, I've replaced that class with the newest version of the class and set the same properties as we had originally.
>>
>>Unfortunately, all defaults seem to change. The new control has more properties than original and defaults are now different as well.
>>
>>Therefore, my question is - is there some simple way to save the default values of the old class and somehow set the properties in the new class to these original defaults?
>>
>>Thanks a lot in advance.
>>
>>---------------------------------------
>>UPDATE. I tried manually setting all properties of the controls having 2 separate VFP sessions and looking back and forth. I found that OCX properties dialog is very hard to use. I was able to get ~80% match of appearance after spending ~4 hours :(
>>
>>Does someone here use these controls and can tell me if they work OK for them (the very latest version)? The controls are very expensive (~2K single developer's license), so I'd like to hear some feedback.
>>
>>Thanks in advance.