><< Actually the main reason why VFP has problems with some ActiveX controls is because of how strictly VFP enforces the standards of ActiveX controls as opposed to VB. >>
>
>I understand the excuse, but it really doesn't matter when you're trying to deliver solutions. Regardless of where it's really broke if we ever really want to be able to use any ActiveX control that works in VB in VFP the VFP team is going to have to be the ones to address it.

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.

Cheers