Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
WSH Odd Behaviour in Debugger
Message
 
To
07/12/2001 13:22:23
Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
General information
Forum:
Visual FoxPro
Category:
Windows API functions
Miscellaneous
Thread ID:
00591305
Message ID:
00591332
Views:
30
>I'm playing around with the following code:
>
>
>oNet = CREATEOBJECT("WScript.Network")
>oNetDrives = oNet.EnumNetworkDrives
>FOR lni = 0 TO oNetDrives.Count - 1 STEP 2
>   ? oNetDrives.Item(lni) && Displays the drive mapping
>NEXT
>FOR lni = 1 TO oNetDrives.Count - 1 STEP 2
>    ? oNetDrives.Item(lni) && Displays the share name
>NEXT
>
>
>What is happening is that it errors-out on the 4th line (first line inside the FOR loop) with "Unrecognized command verb." The funny thing is that if I hover the mouse over the "oNetDrives.Item(lni)" in the Trace window it shows a value for the drive letter, but if I type it into the Watch window it says the the expression cannot be evaluated. As you may have surmised from a couple other threads recently I am new to this. Any thoughts on what is causing the error and odd debugger behaviour? Thanks!
>
Renoir,

Gee...that looks familiar.< g >

Are you saying that the code runs fine without the debugger? Originally, it (or something similar) was written on Win98SE connected to a Novell network in VFP 6.0. It worked fine (no debugger). I just copied and pasted it into a prg in VFP 7.0. Works fine. Same thing in 6.0 and in stepping through in the debugger.
George

Ubi caritas et amor, deus ibi est
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform