Tom

Thanks for that - I'd found that was the only way around
it - I'm assuming this is a bug ?

Cheers

Lizzie

-----Original Message-----
Just like you can have calculation going on in a sheet
that is not the
activesheet or run code on such sheets/workbook, the
activeproject has no
correlation to the code that is running. Use

thisworkbook.VBProject

--
Regards,
Tom Ogilvy

Lizzie wrote in message
...
Hi.

When you open Excel 2000, it opens a default blank
worksheet.
If I then open a worksheet containing VBA code, and run
the code, why does Excel still think that

Application.VBE.ActiveVBProject

is the project belonging to the default blank sheet, and
not the one belonging to the activeworkbook ?

Is this a bug? I can't see how, when code is actually
running, the project running that code is not seen by
VBA
as the ActiveProject.


.