FOUND IT! Considering that my machine appeared to be the only one having the glitch, I was a little reluctant to do a code change on something that has been working fine for everyone for months. My co-worker and I had received new machines recently, and based on the fact that mine was the only one receiving the error - I checked the the options on both machines and realized that Mine was using an older version of MSCAL.OCX. Registering MSCAL.OCX version 9 solved the problem. One of my co-workers mentioned that she had a similar problem on a 2000 machine using MSCAL.OCX version 10 - and that Version 9 seems to work with the least amount of headaches.

Just thought I'd share the good news - I hope this helps the other people who experienced this problem.

THANKS!!

Tina


>Instead of setting the 3 components of the date, how about doing:
>
>ThisForm.oleCalendar.Object.Value = some_date
>
>>I am responding to this to ask again if anyone found a solution to this - but I have an interesting twist to add - My coworker and I are both running Windows 2000 Professional, both with VFP6 sp5. MY machine bombs out with the error - but hers does not? The program and data files are run off of a server, but VFP is run locally - so could this have something to do with the VFP installation? I thought about trying to re-install VFP and the service pack - but thought I'd check here first. So, has anyone found a solution to this perplexing situation?
>>
>>Thank you!!
>>
>>Tina
>>
>>
>>>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.