>the corperate execs have dictated that 'we will use one tool' and that tool is VB.
>
>our contention is that VFP is better suited to our needs and have the same technology (OLE, 32-bit...) as VB. Our final point is that VFP and VB are both MS developer products that share common components and will eventually become part of the developer studio.
>
>doe anyone have anthing to add?

because VFP is both an ActiveX server and ActiveX container
the integration between VB and VFP is very good

e.g. if you create a VFP .DLL you can call it from a VB program and if you create a new control (VB 5.0 CCE) you can use it in VFP

so you can integrate with what the other teams do

Arnon