- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
The thought also occurred that you may need to add a pause (wait) in there, right after you open the application, but before attempting to do anything else with the application, to allow for load time.
There have been documented issues (on "support.microsoft.com" & "social.msdn.microsoft.com", and other sources) with using the GetObject() and CreateObject() routes, because of similar load time issues. Apparently Microsoft Office applications don't immediately register themselves before starting up, as many other applications do, to help speed up the initial load time. The workaround I read about was to change the focus away from the Office application to something else, then back to the Office application, then wait a bit, then the Office application should have registered itself and can now be used further. That switch of focus seemed to trigger the register process, so that the application can be found.
Here is one of the sources I was reading from.
Wesley Crihfield
(Not an Autodesk Employee)