ACC: OLE Object Error When Setting the RowSourceType Property

Last reviewed: September 17, 1997
Article ID: Q173933
The information in this article applies to:
  • Microsoft Access versions 2.0, 7.0, 97

SYMPTOMS

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

When you set the RowSourceType property of a bound or unbound object frame, you may receive one of the following error messages, depending on the type of OLE object that is contained in the frame:

For Microsoft Excel Charts:

   The operation on the OLE object failed.

   The OLE server may not be registered.

   To register the OLE Server, reinstall it.

For Microsoft Excel Spreadsheets:

   A problem occurred while Microsoft Access was communicating with the
   OLE server.

   Try one or more of the following:
   *Make sure you're connected to the network server where the OLE server
   application is located.
   * Close the OLE server and restart it outside of Microsoft Access. Then
   try the original operation again from within Microsoft Access.
   *Reinstall the OLE server to ensure that it's registered."

For Bitmap Image, WordPad, Media Clip, Microsoft Equation Editor, Microsoft Map:

   Microsoft Access can't read the OLE object because communication was
   interrupted.

   If the OLE server application is located on a network server, make sure
   your computer is connected to it.

NOTE: If you have given the database an Application Title, that title will replace "Microsoft Access" in the messages.

CAUSE

The RowSourceType property is not available for all OLE object types, but because it is available for some, the property is visible on the property sheet for all OLE objects.

RESOLUTION

Remove the setting for the RowSourceType property for the OLE Objects mentioned in the "Symptoms" section.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Open the sample database Northwind.mdb (or NWIND.MDB in Microsoft Access 2.0) and create a new, blank report in Design view.

  2. In Microsoft Access 95 and 97, on the Insert menu, click Object.

    In Microsoft Access 2.0, on the Edit menu, click Insert Object.

  3. In the Insert Object dialog box, click Create From File.

  4. Click Browse.

  5. In the Browse dialog box, locate the Bubble.bmp file in the Windows folder (directory) and click Open.

  6. In the Insert Object dialog box, click OK.

  7. In the report's Design view, right-click on the Object Frame. On the shortcut menu, click Properties.

  8. In the Property sheet for the object frame, select Table/Query from the Row Source Type box.

  9. On the File menu, click Print Preview. Note that you see the following message:

          Microsoft Access can't read the OLE object because communication was
          interrupted.
    

          If the OLE server application is located on a network server, make
          sure your computer is connected to it.
    

NOTE: This message will vary depending on the type of object you have inserted.

REFERENCES

For more information about OLE objects, please see the following articles in the Microsoft Knowledge Base:

   ARTICLE-ID: Q112749
   TITLE     : ACC2: List of OLE 2.0 Features Supported in MS Access v. 2.0

   ARTICLE-ID: Q170531
   TITLE     : ACC: How to Retrieve the Path for Linked OLE Objects
               (7.0/97)


Additional query words: Active X
Keywords : IntpOle RptProp kberrmsg
Technology : ole
Version : WINDOWS:2.0,7.0,97
Platform : WINDOWS
Hardware : x86
Issue type : kbprb
Solution 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: September 17, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.