>>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.
This is a bunch of hooeee. The current version of VFP does a poor job of supporting ActiveX controls. I'll give you an example: Try popping up a Modal VFP form over some ActiveX controls (MapObjects for example). Doesn't work does it. So is this the fault of the ActiveX control of VFP's implementation.
We should not need to make excuses for VFP's sorry ActiveX support.VFP should rise to the level that VB does not vise versa.
>>The trouble with this is most third-party ActiveX controls are tested on VB.
The trouble is that VFP does not support AX controls the same way VB does. Hey isn't this the same company ??? How about sharing some of the code and making this product work.
Thanks, Rod
Rod Paddock Editor in Chief CoDe Magazine President Dash Point Software, Inc. VP Red Matrix Technologies,Inc.
