Renoir,

>
>>Gee...that looks familiar.< g >
>
>I'm trying! Felt very badly about the earlier thread and thought I would really get into it instead of just spouting off what I don't know. :-) Great articles by the way. I'm trying to get my hands on the book, but everyone is telling me it will take over a week to get.

Thanks for the kind words. I'm glad you like the articles. One note about the book (and I'm assuming the Wrox book I mentioned in the other thread), it is geared towards the VBScript or JScript platforms. However, VBScript is quite similar to VFP, so, for the most part all you'll have to fend with are the little idiosyncrasies of it (for example: & is the string concatenation operator rather than +) if you're not terribly familiar with it.

>>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.
>
>No, it crashes and then I open the debugger to check it out. Something odd is that in the debugger if I type "oNetDrives" in the Watch window and expand the node it shows a value of 20 for the Count, but "expression could not be evaluated" for Item. Yet in the Trace window using a "hover" the value shows "F:" which is a valid drive designation. Does that mean anything? Do I have a larger environmental problem going on? I'm using VFP6 sp3 on an NT4 workstation.
>
VFP 6.0 didn't handle external COM references (either in or out of process servers) terribly well. VFP 7.0 is much better. You might have better luck with oNetDrives.Item(lni) rather than the Item collection.