Share via

Automation error: error accessing the OLE registry

Anonymous
2011-01-27T17:52:30+00:00

I have an app that I upgraded from 2000 to 2003. When I run it in Win7 64 bit with Office 2010, it seems to open and run fine till I get to a form that opens a Word document. Then I get this error message:

"Automation error: Error accessing the OLE registry."

App has Microsoft Word 14.0 Object library Reference and compiles fine.

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

  1. Anonymous
    2011-03-15T16:59:52+00:00

    This is a known issue when 2003 and 2010 Office products are on the same computer. There is a DLL conflict between the two. Maybe this may or may not solve the problem:

    Find C:\Program Files\Microsoft Office\OFFICE11\OWSSUPP.DLL

    Rename it to OWSSUPP.DLL.old

    Run the Office 2010 diagnostic tool to repair Office.

    2 people found this answer helpful.
    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2011-03-15T21:13:45+00:00

    Many thanks.

    I didn't have Office 2003 installed, I thought. (It did not show in the All Programs window.) I did have an \Office11 subdirectory, but it did not have an OWSSUP.DLL file (nor did "Search" find one).

    Anyway, I uninstalled Office 2003 and ran Repair for MS Office under Control Panel->Programs and Features (which is a very different setup from Office 2007, where acc to MS it can be accessed from an Office App options page).

    My sample code works now. Still need to test it in the main app.

    Thanks.

    0 comments
  2. Anonymous
    2011-03-15T16:15:32+00:00

    Maybe this will help me get a response--I get the same error with this simple code:

    Private Sub Command5_Click()

      Dim oWord As Object

      Dim sCurrentPath As String

      'Set oWord = CreateObject("Word.Application")

      If Not oWord Is Nothing Then

         oWord.Visible = True

      End If

    End Sub

    I think this approach should work as "late binding," but I've tried it with and without a reference to MSWord.olb.

    The error does not occur at 'Set oWord = ...' but at the 'oWord.Visible = true' line.

    Running Office 2010 32-bit version in Windows 7, 64-bit version.

    0 comments