>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.

I have not seen this poll. Are you saying most VB programmers prefer the VB UI, or Most desktop users prefer the VB UI. Can you give me an example of the difference between a control's appearance (include the control name) as presented in a VB form and a VFP form.
>
>>>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.

I think they call that 'Optimizing'. Having created forms that have several instances of treeviews or Listviews (both in code and click-and-drop), and never experienced this problem. I do try and capture all images in a single ImageList (I'm an optimizer hanger on, I guess), Could you give an example of how this fails for you? I am always interested in VFP bugs?
>
>
>>>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).

There is the suspicion that VB programmers have 'difficulty' issues with the VFP language. The discipline is demanding. But - there are those that prefer riding to driving. The goal of a development platform is to provide as much usefulness to the end-user, and less to the point that it needs to be 'easy' for programmers. If this were the case, C and BAL would be outlawed:). Some developers will say that VB doesn't allow them to provide the same level of usability (despite the discipline overhead), as they can with VFP. It's seems your saying that VFP is just difficult for you to work with, correct?

>
>Thank you