>>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?

Fred