Fritsche

Sorry, but I can´t see how the Resource Kit can help me by the task that I have described in the opening posting.

May be you can use the Microsoft Active Accessibility technology instead. See this Topic.

You can analyse the Commandbars with Microsoft Active Accessibility. See this Topic.

Analyse the Commandbars with Microsoft Active Accessibility. See this Topic.

Some weeks ago I got the task to automatic create a lot of databases with the Access 2003 Source Code Control Add-in in a nightly build. First I use the AutoIt Functions like WinActivate and ControlClick. But many Controls in MS-Office, such the menubar (MsoCommandBar) or buttons (bosa_sdm_Mso96) are not visible to those commands. So I use many Send or ControlSend commands. Finally the Build runs not stable. After 10 or 30 minutes it blocks with unreproducible errors. Then I rewrite the scripts by use of the Microsoft Active Accessibility technology. Now I can address the MS-Office controls by name. I can click at a menu item by use of an object model. The problems are disappeared. I attached a library with some examples. For now I use a small COM-Wrapper for the Win-API Calls because the Win-API returns a COM-Object (IAccessible) in their parameter list and I can´t implement that in AutoIt. May be someone out there have the knowledge to replace it with pure AutoIt Code. If you find it useful, please feel free to extend the library or the examples. Best Regards ActiveAccessibilityForMsOffice.zip