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

Article translations Article translations
Article ID: 295179 - View products that this article applies to.
This article was previously published under Q295179
Moderate: Requires basic macro, coding, and interoperability skills.

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

Expand all | Collapse all

On This Page


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.


Article ID: 295179 - Last Review: June 8, 2004 - Revision: 4.3
  • Microsoft Office Access 2003
  • Microsoft Access 2002 Standard Edition
kbprogramming kbvba kberrmsg kbprb KB295179

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from