VBA objects in 2010

[Asator]

This works in 2003:

Dim xlApp As Object
Dim wrdApp as Object
dim objOL as Object
...code...
Set xlApp = New Excel.Application
Set wrdApp = New Word.Application
Set objOL = New Outlook.Application
...code...
Set xlApp = Nothing
Set wrdApp = Nothing
Set objOL = Nothing

In 2010, it bombs out on Set xlApp = New Excel.Application or Set objOL = New Outlook.Application

Did something change in COM that would break this? It seems to die on different objects on different machines. Is the registry hosed? Both the machines were upgraded from 2003.

Basically the code opens up instances of each application, does a bunch of stuff in the background, then closes them (or at least its supposed to).

 

[pbornemeier]

Are the appropriate items reference in the VBE using Tools | References ?

Does this sequence cause the same probmem?

    Dim appWD As Word.Application
 
    Set appWD = CreateObject("Word.Application")
    appWD.Visible = True
 
    ...code...
 
    Set appWD = Nothing

 

[Asator]

Yes.. all the references are enabled.. CreateObject fails too (that's actually what I had originally, then switched to what I have above after it started puking in 2010.

What's odd is, if I open a new instance excel (for example) before I run this, it'll run, error out, and there will be a second instance of excel.exe launched. If I then remove the "new" from the set xlapp line and run it again, it works fine. Very odd.

 

[Asator]

Bump!