Dave,

You are not the only one experiencing this problem. I did too.

Nond..

>>>>>Has anyone experienced the loss of the Value property with this version of the M$ Calendar Control (it was loaded with Access 2000)?
>>>>>
>>>>>Access still shows a Value property, while the properties dialog of the control in VFP no longer shoes the Value property.
>>>>>
>>>>>A work around using the month, day and year properties exists, but that is a pain.
>>>>>
>>>>>TIA,
>>>>>Dave Emerson
>>>>
>>>>Try the Calendar.Object.Value
>>>
>>>I think you may have misunderstood me or I am misunderstanding you. I have dropped the ActiveX Calendar Control on a form. When I select that object, the properties dialog does not have a Value property. Prior to installing Access 2000, a calendar object did have that property.
>>>
>>>I have tried it in both VFP 5 and 6 with the same results. Which is to be expected since they both use the same OCX.
>>>
>>>When the executable is recompiled, the Value reference causes and error. Older versions of the executable do not experience the error.
>>>
>>>Dave
>>
>>Several common ActiveX controls were broken between VFP 5 and 6 - or rather, broke code that originally worked fine in VFP5.
>>
>>One of the main things was that certain properties that used to be obtained right off the object - e.g., thisform.oleCalendar.Value - must now be obtained through the Object - e.g., thisform.oleCalendar.Object.Value.
>>
>>Are you using the properties dialog to set the Value? If not, then there's no reason to look there.
>>In your code, change the oleCalendar.Value references to oleCalendar.Object.Value
>>
>>"oleCalendar" is just the example name I am using, but "Object.Value" is the actual code replacement.
>
>That did it. Thanks Trey.
>
>When in the *#()*#%@* blazes did that stupid (IMHO) idea get put through? Anyway thanks again.
>
>Dave