Run-time '429': ActiveX component can't create object

[jgelpi16]

I have the below function that always crashes on the highlighted line. I have the following libraries added....Help please.

Libraries:
Visual Basic For Applications
MS Access 14.0 Object Library
OLE Automation
MS Office 14.0 Access database engine Object Library
MS Excel 14.0 Object Library


MS Outlook 14.0 Object Library

Function IsExcelRunning() As Boolean
    Dim xlApp As Excel.Application
'On Error Resume Next
    Set xlApp = GetObject(, "Excel.Application")
    IsExcelRunning = (Err.Number = 0)
    Set xlApp = Nothing
    Err.Clear
End Function

[ajetrumpet]

you should not be using GETOBJECT when you've created it with a DIM. when you DIM an excel object, you need to use the NEW keyword. that will start the actual program process, if I remember right. dimming a var as an excel object doesn't initialize the program (I don't think). it simply assigns a type of object to the var. This looks like late binding and early binding combined, which aren't meant to work together.

try replacing that line with:

SET xlApp = NEW excel.application

that will start it. but you won't be able to see it unless you changed it's .visible property afterwards.

[jgelpi16]

Great, thanks for the explanation!

[jgelpi16]

Adam - I just reviewed the code. I am actually attempting to check of Excel is already open. So maybe I'm approaching this from the wrong angle?

[ajetrumpet]

Adam - I just reviewed the code. I am actually attempting to check of Excel is already open. So maybe I'm approaching this from the wrong angle?

you want to CHECK to see if it's open? well there's a number of ways you can do that. the easiest would be to throw an error on purpose. for instance, use this code:

Set xlApp = GetObject(, "Excel.Application")

run it, capture the err.number it throws and put an err routine in it for that number. If the err.number = 0, obviously it's already open. OK...NOT "open", but the process is running. that's what GETOBJECT() does (I think). It'll fail if the process isn't running.

the other way would be to loop your system process list, but obviously that takes more code. it takes an API, which I have in my archives. but the err method is better, to me anyway.

[jgelpi16]

That helped. The code I was actually running was correct. I commented out the "On Error Resume Next" piece, which was part of the functionality. Your above explanation triggered my thought process. Thank you.