>No. To augment VFP where VFP is lacking and to give you more flexibility as a >developer - yes.

Thats fine for tomorrow - if the needed enhancements are put into the product. No pun intended here - but what are you going to do today????

>The problem really is that, in a worst case scenario, majority of VFPers will >not go on VB for sure because of contrasting structure of the two (OOP, >Object-Based).

Thats very interesting - because many VFP developers don't really take advantage of OO. Yes, many use inheritance - way too much. I suspect this is the reason why folks would not migrate to VB. However, this would also tell me that many folks have not reasearched the problem enough.

With creating ActiveX Controls in VB, you get 1 level of inheritance. Also, there are some creative things you can do with regard to interfaces. Is it as clean as VFP - no. But, thats not to say you can't do some cool things in VB.

The issue in VB is with its containership scenario. Creating user controls is a bit of a pain if you take a VFP approach to it. However, if you take a design pattern approach - things are a bit more cleaner. Don't get me wrong, VFP's object model is nicer. But, you can do a lot in VB as well.