>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
1. UI look "smarter" than VFP.
2. It rarely cause Illegal operation when using ActiveX control compare with VFP (VFP always cause illegal operation if i use ActiveX control in my experience)
3. It is easier to code, because since it is not OOP, therefore i don't need to change my code even I change my screen.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

I think that there are some good reasons, at times, to use VB rather than VFP. I'm not sure I follow all of your points above, though.

1) 'UI look "smarter" than VFP.' Not sure what you mean by "smarter" here. Maybe you mean that your users already have apps built in VB and like the look and feel, and consider it professional and standard. That's fine, and it makes a lot of sense to keep these sort of user preferences in mind. But, the odds are pretty good that you could duplicate the same exact look and feel in VFP (it's pretty close anyway -- though some default sizes of controls are a little different; but you could subclass these and change them to match exactly the VFP feel).

2) This one I give you -- if you are using external controls or libraries the odds are much better that they were designed with VB in mind, and tested under VB, rather than Fox.

3) 'It is easier to code, because since it is not OOP, therefore i don't need to change my code even I change my screen.' Not sure what you mean here.... maybe you mean that when you change a screen in VB it doesn't affect other screens. But, there's no reason it has to do so in VFP. You can change the lowest class level. Again, though, I think I am not sure of what you are getting at here.


Again, I am not trashing VB by any means. There are definitely cases where I choose VB over VFP for projects... I just don't think that all of the points you mention outweigh the speed benefits that you seem to need.

Just my two cents. Hope it helps a bit.