Val:

Have found a few threads that suggest:

=====================
1)using sys(2333, 0)
=====================

into the Load() of the form. See if that helps. I am not completely sure what it does but I had a similar problem and it did the trick.

From our friend the MSDN Library:

If an ActiveX control does not perform properly when the control is instantiated, issue SYS(2333) or SYS(2333, 0) before the control is instantiated to disable dual interface support for the control. After the control has been instantiated, issue SYS(2333, 1) to enable ActiveX dual interface support for any controls that are later instantiated.

=====================
2) setting AUTOYIELD
=====================

_VFP.AUTOYIELD=.F., read the help about this command and activex controls, thats could be the problem, try the sys(2333)


let me know what u find.



>I have had the same problem and am trying to resolve it now.
>
>Not sure what's going on.
>
>Val Matison
>
>
>>Did u ever resolve this problem? If so, what was the solution?
>>
>>thanks...
>>
>>>Has anybody had any problems with the Calendar control under Win2K, the problem I am having is:
>>>
>>>I have a form with the Calendar control on, the form accepts a parameter which can be any date, this is then split and the appropriate properties: Day, Month and Year are set with the parameters. Yet the problem I am getting is:
>>>
>>>Error Number 1426 Method Init,
>>>OLE Error Code 0x8002802b Element Not Found.
>>>
>>>This happens three times, (Day,Month and Year Properties.)
>>>
>>>The same application works under Windows 98.
>>>This also seems to do exactly the same under VB6, Any information about this would be greatful.