>Ok - I have two questions - one practical to get my app fixed and one "seeking knowledge" regarding my Calendar control problems in general since installing 6.0 on the same machine as 5,0.
>
>1) I can now access the current date via calendar.object.value - great. But - how the heck do I set it? attempts at calendar.object.value = date() or calendar.object.value = datetime() or the character versions of those values all end up with a "type mismatch" error.
>
>2) OK any active x experts please enlighten me - I only want to UNDERSTAND!!! What happened in the install to CHANGE the way this works??? I see that 6.0 isntall created a MSCAL.ocx for version 8 of the calendar, BUT my old form does not reference it! It still refrences the old msacal70.ocx which, unless I'm crazy, hasn't changed. So - the question is - If I'm referencing the same old OCX from the same old form in the same old 5.0a version of VFP - HOW CAN IT POSSIBLE WORK DIFFERENTLY???? There's nothing else involved is there???
>

This one's easy - they both are referenced by the same ProgID, which is the basis used to instantiate the object. When the ProgID changed in the registry to point to the new control, anything that used to talk to the old control is now redirected to the new one, and it simply isn''t the same thing. You have two choices; re-register the old control and force the VFP6 app to use the old control, or update the VFP5 app form to use the new control.

>Sorry for the all caps - but this is really frustrating.
>
>Ken