BUG: Calendar Control in Visual Basic Causes Application Error

Last reviewed: May 20, 1996
Article ID: Q143116
The information in this article applies to:
  • Professional Edition of Microsoft Visual Basic, 16-bit only, for Windows, version 4.0
  • Microsoft Access Developer's Toolkit, version 2.0
  • Microsoft Office for Windows

SYMPTOMS

A 16-bit Visual Basic program containing the calendar control from the Access Developer's Toolkit, version 2.0 causes an application error if Microsoft Office is running in the background and you run the Visual Basic program in a 32-bit operating system. This behavior does not occur under the 16-bit operating system.

STATUS

Microsoft has confirmed this to be an issue in the Microsoft products listed at the beginning of this article. Microsoft is researching this issue and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce

  1. Start 16-bit Visual Basic 4.0, or if it is already running, click New Project on the File menu.

  2. On the Tools menu, click Custom Controls. Click MSACAL20 to add the calendar control from the Access Developer's Toolkit to Visual Basic. Click OK to close the dialog box.

  3. Add the calendar control to the Form1 form.

  4. On the Run menu, click Start or press the F5 key to start the program. When you stop the program an application error occurs with the following message and Visual Basic ends:

          VB caused a general protection fault in module MSACAL20.OCX at
          0003:0000153d.
    


Additional reference words: 4.0 vb4win vb4all
KBCategory: kbbuglist kbusage
KBSubcategory: PrgCtrlsThird


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 20, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.