>the object .oIE shows in the debugger but it's properties cannot be evaluated.
>
>
>wierd

Not too weird, though, we've seen this many times. Some COM objects have a path to their tlb, some show some other type of interface, so the debugger may or may not know how to read their properties. Also, there are many COM objects where the properties actually don't exist, there's only a get method, equivalent to an _assign.

However, it doesn't mean that you can't use intellisense to dig them out. Intellisense seems to read the PEMs in a different manner, and most of the time it can see what debugger can't.

Another tip for IE and Office objects - even intellisense can't drill too deep in the object hierarchy. So if you need to drill down to another object (member or reference, you never know), assign that object to a temp variable, then run intellisense on that one. Many times that's the only way to get deeper in.