>>Hi John!!! Glad to see you made it!
>
>Glad to be here!!
>
>>I think there is one thing that has not been mentioned...application development and maintenance. With OOP UI elements in VFP and missing in VB, VFP takes a HUGE lead here.
>
>Yes, the OOP features in VFP are superior to VB. And, the VFP IDE is much superior to VB's for the most part. However, I can not justify using a tool as a C/S front end just because it is OOP. If I have to choose between overall performance and OOP - I will choose. Think of client. Doe he/she really care of it is OOP. As developer's - its a big issue to us. From a client's perspective - performance is the key. With the ability to create ActiveX controls in VB - I think I could still get pretty close to what I do in VFP. In my situation, I do not rely on inheritance all that much. Rather - I rely on design patterns - which are applicable in VB.

Some clients care very much whether an app is OOP or not. Just before I left my last contractor employer who did mostly work with the government, I was beginning to notice that most contracts required OOP to be implemented. Granted, in the private world, if the app works, the client will be happy.

Steve