<< I already stated this in my post. But to take the point one step further, I don't believe it's the VFP team's or the VB team's responsibility to clear this up. I believe it's the responsibility of all the development teams of the tools that make up VS to get together and make sure all the products handle global things (like ActiveX) in the EXACT same way. >>

In theory I agree, but I think the Fox team is pretty much out of the loop with the rest of the VS team - not to start a thread on this, but if development parallels marketing, then that's certainly the case - VB is the standard for OCX support if the Fox team makes its OCX support the same I'll be happy. Plus that'll let us say it don't work in VB either!