>>In addition to some of the interesting discussion in the "JVP Challenge" thread, I have frequent needs to create components that behave well with other technologies, such as Active Directory. My understanding is that VB plays much better in this arena, and I find that alone to be a sufficient reason to learn more.
>
>Rick's article on VFP's troubles instanciating the ADSI object is inaccurate. VFP plays just fine. I have written a user manager, a print queue manager, and a resource and service manager using ADSI in ALL VFP. There are plenty of reasons to learn VB, but ADSI interoperability is not one of them.

I tried to use ADSI last year with VFP and ran into some problems. Things that worked in VB, didn't in VFP. I even had JVP look at some of it. Neither of us got it to work. Has there been a revision of ADSI or did SP3 impact that, or were we just stupid?<g>