That's something to find out in the debugger. Is oApp valid at that point?
Is there an ActiveInspector object? It's hard to debug when multiple dot
operators are used, any break in the chain of instantiated items can cause
that error.

Are you keeping alive references to things you add that must be global or
module level? Unexpected garbage collection is a very common problem with
..NET code, things get collected and no longer are valid object references.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Paul Heinisch" wrote in message
...
I did that...but I'm still getting an error message bject reference not
set
to an instance of an object....on this line:

Dim cmdBars As office.CommandBars = oApp.ActiveInspector().CommandBars

What am I doing wrong? Thanks for your help!

Paul