Article ID: 311219 - View products that this article applies to.
This article was previously published under Q311219
Clients that use early binding to the Microsoft Calendar control (Mscal.ocx) may encounter unexpected errors or invalid data or may crash because of stack corruption when the properties or methods of the control's ICalendar interface are called. The problem occurs on computers that have recently had Office XP installed.
Version 10.0 of the Calendar control, which ships with Office XP, contains added methods to support assigning Font objects by reference (putref) for the following properties:
All clients that use Mscal.ocx should use late (DISPID) binding to call methods on the ICalendar interface.
Microsoft Visual Basic (VB), Visual Basic for Applications (VBA), and MFC control containers are not normally affected by this problem because they use late (DISPID) binding by default. Active Template Library (ATL) control containers that use #import are more likely to encounter the problem, and can use CComDispatchDriver to wrap the control to make late-bound calls.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Steps to Reproduce Behavior