>>I used to be able to reference the .Value property directly in 5's but no
>>longer can in 6's. You must now reference it through oCal.Object.Value.
>
>That's an intentional change: when there's a potential conflict between an ActiveX Control's property and a VFP property, you have to refer to the Object.Property, instead.
That makes MUCH more sense to me. I was wondering why some properties could still be accessed without the .Object reference.
>
>>There also seems to be a problem with setting the value. I can't get that to
>>work in 6's, but you can set the .Month, .Day, .Year properties and at least
>>that works. Shouldn't you just be able to:
>>oCal.Object.Value = DTOT(DATE()) ?
>
>I was just able to get that to work by using
oCal.Object.Value = DATE()<\CODE>. Have you tried?
I've tried setting it to Date type (including DATE()), datetime type, numeric, and character types. ALL of them produce the "type mismatch" error for me.
Fred
