Christof....

That is not the context of the issue however. The context relates to middle-tier development. So, ActiveX Controls really would not be that big of an issue. With regard to the additional elements you would load with VB - lets remember that there are many things you can do with those objects that you cannot do in VFP. All of that said, I would still contend that a VB app on average is leaner than a VFP app.

As far as ActiveX Controls are concerned, if you are going to compare apples to apples - if the VFP app needs an ActiveX Control - the VB one will need the ActiveX Control as well. Therefore, the ActiveX Control is required - thus making it irrelevent to the decision - since it is not a variable factor.



>Hi John,
>
>>Lets remember, it takes about a mb to load VB. It takes over 3 mb's to load VFP the first time.
>
>The runtime, I suppose. But if you add all the programs necessary to access data, a report writer, all these ActiveX controls that are necessary in VB but not in VFP, I think you would get different numbers.
>
>Christof