ADT2: "There Is No Object in This Control" Error Message

Last reviewed: May 14, 1997
Article ID: Q130335
The information in this article applies to:
  • Microsoft Access Developer's Toolkit version 2.0

SYMPTOMS

Novice: Requires knowledge of the user interface on single-user computers.

When you insert a Calendar control into a new form and then try to print the form while the form is open in Design view, you may receive the following error message:

   There is no object in this control.

NOTE: The Calendar control is available only with the Microsoft Access Developer's Toolkit.

RESOLUTION

To work around this problem, choose Save or Print Preview from the File menu before you print the form.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access version 2.0. This problem no longer occurs in Microsoft Access for Windows 95 version 7.0.

MORE INFORMATION

Steps to Reproduce Problem

  1. Open an existing Microsoft Access database.

  2. Create a blank form.

  3. From the Edit menu, choose Insert Object.

  4. In the Insert Object dialog box, select the Insert Control option button.

  5. In the Control Type box, select Calendar Control, and then choose the OK button.

  6. From the File menu, choose Print.

  7. In the Print dialog box, choose the OK button. Note that after a few seconds, you receive the error message:

          There is no object in this control.
    

REFERENCES

Microsoft Access Developer's Toolkit "Advanced Topics," version 2.0, Chapter 6, "Using OLE Custom Controls," pages 163-175


Keywords : FmsOthr kberrmsg
Version : 2.0
Platform : WINDOWS
Hardware : X86
Issue type : kbbug
Resolution Type : kbworkaround


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 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.