Public Sub Main()

        '**** Dimension Local Variables ****
        Dim XL As New Excel.Application()
        Dim VBProject As VBIDE.VBProject

        '**** Access VB Projects ****
        For Each VBProject In XL.VBE.VBProjects
        Next VBProject

        '**** Close Excel Application ****
        XL.Quit()
        XL = Nothing

    End Sub

When the application terminates and the garbage collection is called,
the Excel application crashes and returns:

    OleMainThreadWndName: excel.exe - Application Error

    The instruction at "0x77b26033" referenced memory at "0x01144a94".
The
    memory could not be read.

I'm running NT and Excel 98. To work around I'm currently calling a
VB6 .dll that performs the required task (stripping VBProjects from an
Excel workbook) but that is a less than perfect solution.

Any ideas anyone?

You'll get the same error in VB6.

Richard,

Is that a solution or an observation? If it's a solution I don't
understand. Can you elaborate?

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Like many of the office object models, the parent object -- in this case,
the Excel.Application -- when called, brings up Excel and automates the
process of starting the application with a default workspace, book and
sheets.

Because of this, simply closing down Excel doesn't assure proper closure of
these objects. That's why I suggested you close these objects out before
setting the excel.application to nothing.

When you instance an Excel application via OLE:

   Dim XL As New Excel.Application

The application is created blank with no worksheets, workbooks or
add-ins. I believe MS did this to speed up the OLE creation of
application objects.

The code example I posted creates an application with nothing open
(including no VBProject objects).

If the following two lines are removed it works perfectly.

     '**** Access VB Projects ****
     For Each VBProject In XL.VBE.VBProjects
     Next VBProject

It also works even if you access the VBProjects.Count property. But as
soon as the VBProjects is enumerated it causes problems.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Thanks for helping me out.