Using automation causes a Run-Time Error when only the Microsoft Access Runtime is installed on a computer

Support for Office 2003 has ended

Microsoft ended support for Office 2003 on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article was previously published under Q295179
This article has been archived. It is offered "as is" and will no longer be updated.
Moderate: Requires basic macro, coding, and interoperability skills.

This article applies only to a Microsoft Access database (.mdb).

When you use Automation to create a new object in a Microsoft Access run-time application on a computer that does not have the full version of Access installed, you receive the following error message:
Runtime error -2147023181

Automation error:Connection to type library or object library for remote process has been lost.
The CreateObject call is not supported in the run-time environment because the Access runtime requires a file to be supplied on the command line.
This behavior is by design.

Steps to Reproduce the Behavior

  1. Install an Access run-time solution on a computer that does not have Access installed.
  2. Install Microsoft Excel, Microsoft Word, or some other Microsoft Visual Basic for Applications (VBA) enabled application.
  3. Open the application that you installed in step 2.
  4. Press ALT+F11 to start the Visual Basic Editor.
  5. In the Visual Basic Editor, type the following line in the Immediate Window:
    Set oApp=CreateObject("Access.Application")
  6. Press ENTER.

    Note that you receive the error message that is mentioned in the "Symptoms" section of this article.
pra inf prb runtime OLE automation ACC2002 ACC2003

Article ID: 295179 - Last Review: 12/06/2015 01:53:57 - Revision: 4.3

Microsoft Office Access 2003, Microsoft Access 2002 Standard Edition

  • kbnosurvey kbarchive kbprogramming kbvba kberrmsg kbprb KB295179