ACC2000: Access Automation Causes Run-Time Error -2147467259ID: Q209157
|
While opening Microsoft Access and a form through Automation and setting focus to the the form custom menu bar, the following Microsoft Visual Basic error message occurs:
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 the Automation code executes.
Microsoft provides programming examples for illustration only, without warranty
either expressed or implied, including, but not limited to, the implied warranties of
merchantability and/or fitness for a particular purpose. This article assumes that you
are familiar with the programming language being demonstrated and the tools used to
create and debug procedures. Microsoft support professionals 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 needs. If you have limited
programming experience, you may want to contact a Microsoft Certified Solution Provider
or the Microsoft fee-based consulting line at (800) 936-5200. For more information about
Microsoft Certified Solution Providers, please see the following page on the World Wide Web:
http://www.microsoft.com/mcsp/For more information about the support options available from Microsoft, please see the following page on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.aspTo work around this behavior, use either of the following methods:
Function AutomationTest()
On Error GoTo AutomationErr
<Automation code goes here>
AutomationExit:
Exit Function
AutomationErr:
If Err.Number = -2147467259 Then
Resume 'until control is visible.
Else
<handle any other errors>
End If
End Function
Private Sub Form_Timer()
Me.TimerInterval = 0
Application.CommandBars.ActiveMenuBar.Controls(1).SetFocus
End Sub
This run-time error occurs only while using 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.
Menu Name: Message
Menu Macro Name: Macro2
Status Bar Text: <leave blank>
Message: Hello
Beep: Yes
Type: None
Title: <leave blank>
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"
objAccess.CommandBars.ActiveMenuBar.Controls(1).SetFocus
End Function
For more information about Automation, in the Visual Basic Editor, click
Microsoft Visual Basic Help on the Help menu, type "understanding Automation" in
the Office Assistant or the Answer Wizard, and then click Search to
view the topic.
Additional query words: prb
Keywords : kbdta
Version : WINDOWS:2000
Platform : WINDOWS
Issue type : kbprb
Last Reviewed: July 6, 1999