Vista - Microsoft Script Debugger Locals Window Doesn't display VBScript COMobject Data

Hi,

I have been wrestling with this problem for hours and can't seem to
find any posts or answers to this question.

I am trying to debug some vbscripts that launch internet explorer and
web pages. I am trying to use the locals window to see the Internet
Explorer object data or other programs COM object data, but for some
reason it does not give me a plus or minus sign to drill down into the
object to see all the data for each of the properties or methods. I
have tried 3 different debugging tools and have the same problem on
each.
1. Microsoft Script Editor
2. PrimalScript 2009
3. Admin Script Editor

All 3 of them give me a plus or minus sign to drill down into the
WScript object to see all the data for each of the WScript properties
or methods but will not give me that functionality on the COM or other
application objects.

I can write VBA code with Excel VBA and it's locals window will
display a plus or minus sign drill downs for the COM and other
application objects just fine, but I can't seem to get any of the
vbscript editors to display that. I have seen screen shots of
PrimalScript being able to drill down into the COM objects, but for
some reason I can't on my computer.

I am running Windows XP Professional with SP3. Would anyone be so
kind and friendly as to help me with some ideas to fix this problem?

Thanks!
Shawn

Shawn wrote:A script debugger can't be used with compiled code. You need to use visual
studio.

--
Microsoft MVP - ASP/ASP.NET - 2004-2007
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Thanks for your response. Someone just sent me the solution. It
appears I had some .dll files out of date.

I had to update the following .dlls - pdm.dll and msdbg2.dll

in the following folder.

C:\Program Files\Common Files\Microsoft Shared\VS7DEBUG.

After updating those and reregistering them with regsvr32 the problem
was resolved and all three script debugging programs now update the
locals window with the objects data making troubleshooting
significantly more effective and efficient.



On May 16, 1:58*pm, "Bob Barrows" <reb01...@xxxxxx> wrote: