You may receive the "Run-time error -2147467259" error message when you open a form by using Automation in Visual Basic .NET

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

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

For a Microsoft Access 2000 version of this article, see 209157.
Expand all | Collapse all

On This Page


When you open Microsoft Access and a form through Automation and set focus to the form's custom menu bar, you receive the following Microsoft Visual Basic error message:
Run-time error '-2147467259 (80004005)':
Method 'SetFocus' of object 'CommandBarPopup' failed


SetFocus fails because the control (in this case the menu bar) is not visible in the user interface at the time that the Automation code is executing.


Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements. To work around this behavior, use either of the following methods.

Method 1: Trap for the Error

Enter a function similar to the following:
Function AutomationTest()
   On Error GoTo AutomationErr

   <Automation code goes here>

   Exit Function

   If Err.Number = -2147467259 Then
      Resume    'until control is visible.
      <handle any other errors>
   End If
End Function

Method 2: Insert a Time Delay

Set focus by using code behind the form instead of the Automation code. For example, set the form's TimerInterval to 1000 (the value assigned may vary), and then add the following code to the form:
Private Sub Form_Timer()
   Me.TimerInterval = 0
End Sub


The run-time error that is mentioned in the "Symptoms" section occurs only when you use Automation. The occurrence varies based on whether or not Access is idle after the form opens, but before the Automation code attempts to set focus to a control. Variations in CPU speeds, program timing, and operating systems may cause this behavior to occur on some computers, but not others.

Steps to Reproduce the Behavior

  1. Start Access.
  2. Create a new database named Db1.mdb in the C:\ folder.
  3. In the Database window, click Macros under Objects, and then click New.
  4. Under Action, add the AddMenu action, and under Action Arguments, set the following arguments:
              Menu Name: Message
        Menu Macro Name: Macro2
        Status Bar Text: <leave blank>
  5. Save the macro as Macro1, and then close it.
  6. Create another new macro.
  7. On the View menu, click Macro Names.
  8. Under Macro Name, type Message, under Action, add MsgBox, and under Action Arguments, set the following arguments:
        Message: Hello
           Beep: Yes
           Type: None
          Title: <leave blank>
  9. Save the macro as Macro2, and then close it.
  10. In the Database window, click Forms under Objects, click New, click Design View , and then click OK.
  11. If the property sheet is not already displayed, click Properties on the View menu.
  12. Click the Other tab in the property sheet, and then scroll down to the MenuBar property.
  13. Set the MenuBar property to Macro1.
  14. Save the form as Form1, and then close the form.
  15. On the File menu, click Close, and then on the File menu again, click New Database to create another new database.
  16. Create Db2.mdb in the C:\ folder.
  17. In Db2.mdb, click Modules in the Database window, and then click New.
  18. Add the following code:
    Option Compare Database
    Option Explicit
    Dim objAccess As Access.Application
    Function AutomationTest()
       Set objAccess = CreateObject("Access.Application")
       objAccess.Visible = True
       objAccess.OpenCurrentDatabase ("C:\Db1.mdb")
       objAccess.DoCmd.OpenForm "Form1"
    End Function
  19. Click Compile Db2 on the Debug menu, and then click Save Db2 on the File menu. Save the module as Module1.
  20. Click anywhere within the AutomationTest() function, and then click Run Sub/UserForm on the Run menu.
NOTE: After the second instance of Access is generated by the Automation code, click Microsoft Visual Basic on the taskbar to see the error message that is mentioned in the "Symptoms" section.


Article ID: 286126 - Last Review: March 29, 2007 - Revision: 6.3
  • Microsoft Office Access 2003
  • Microsoft Access 2002 Standard Edition
kbprogramming kbautomation kberrmsg kbprb KB286126

Give Feedback


Contact us for more help

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