Hi,

>>1) 'UI look "smarter" than VFP.
What I meant "smarter" here is, VB control and UI look more attractive compare to VFP. Most of the users prefer VB as GUI.

>>2) Most that develop with VFP rarely get ActiveX errors. The MS 6 OCX is pretty stable. When I first started using them, I had some problems, but they were programming errors. You should message any ActiveX errors you encounter to the board.
I have experience on using MSCOMM32.ocx in VFP. If i have more than one instance of MSCOMM.ocx in my application (each per form), my application cause illegal operation. I change the way of my programming, that let all forms shared one instance of MSCOMM32, i work fine.


>>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.'
Since VFP is OOP programming language, therefore i have to change my coding if the hierarchy of my control was changed
(e.g. thisform.pageframe1.page1.mycontrol -> thisform.mycontrol).

Thank you