>OK. Here's the story:
>
>Changing the month on the MonthView by clicking on the Next Month or Previous Month buttons or by clicking on a visible date not in the current month invokes the form's Error method. In my case, the CodeBook 6.1 form has an error handler in the base form class, so it reports the error.
>
>The interesting thing is that if I remove all code from the Error event, the FoxPro error handler is not invoked and the control works just fine. Actually, if I Ignore the error the control works fine too.
>
>Now the question becomes: Where do I point the finger of blame for this situation? The MonthView control for somehow invoking the Error event? FoxPro for not fielding the error if I have no code in the Error event? Or is it just that "This behavior is by design"?
>
>...Jim

You're right, it is firing the error method. It's error 1426, "OLE error code 0x". I guess you could just trap for that and skip it, but I don't see why it happens, either. Nothing I've tried seems to get rid of the error (SYS(2333) or _VFP.AutoYield in the form Load, NODEFAULT in the object Refresh method).