>>>>Has anybody noticed that VFP6.0's calendar control (MSCAL.OCX) works slightly different from VFP5.0 (MSACAL70.OCX)?
>>>
>>>Yes, we need to take care of that as well. The best we've found is to check for the existence of the value property. If it is not there, you concatenate the day/month/year properties into a value property of your own.
>>
>>Yes, but I get the "type mismatch" problem whenever I try to set the .Value property. You mean you can set it?
>
>What I know is that control changes from version to version. We ended up to use our own Value property. I can't understand why this control is changing that much. After all, it's only a calendar. But, it might get better with the release. The best is to not waste too much time when you have a bug like this on a beta version.

True enough. At least setting the individual properties works!

Fred