Hello,
      I have an application in which i am using the GetObject function to detect if there is an instance of Excel currently running.

The code is below. I have checked the task manager to ensure there are no instances of excel. Every time i run the code it ends up creating the excel object. Any one ever see this behavior?


Thanks


Private Sub GetExcel()

        Dim myxl As New Excel.Application

        On Error Resume Next

        myxl = GetObject(, "Excel.Application")
        If Err.Number <> 0 Then
            MessageBox.Show("Excel is not running")
        Else
            MessageBox.Show("Excel is running")
            myxl.Application.Visible = True
        End If

    End Sub

J. David Hock

Hello all,
        If anyone is interested i have been experimenting and found some interesting things. I created a new project and put the following code into a button click event



        Dim myxl As object

        On Error Resume Next

        myxl = GetObject(, "Excel.Application")
        If Err.Number <> 0 Then
            MessageBox.Show("Excel is not running")
        Else
            MessageBox.Show("Excel is running")
            myxl.Application.Visible = True
        End If



This produced the results I was hoping for, when excel is not running it shows the "Excel is not running message" and if I open an excel workbook and run it then I get the "Excel is running" message.

The difference between this sample app and the app that I have created is that I removed all references to microsoft office and microsoft excel. I also had to rem out any code that had to do anything with Excel. If someone could repeat this that would be great.


Thanks

J. David Hock

> Every time i run the code it ends up creating the excel object.

Well OF COURSE it works like you said!
The NEW operator *specifically* is used to CREATE AN INSTANCE of the specified class!!!

So every time you use NEW, you are asking to create something...in this case, Excel!

All you had to do was get rid of the NEW:
But please, please, please stop using ON ERROR RESUME NEXT. I can't believe MicroSloppy was crazy enough to leave that in VB.NET!