>Obviously a poor example. Sorry for the second slip Sergey :-)
>
>Lets try an ActiveX listview versus the ListBox in VFP. The question is, why would I use ActiveX controls instead of native VFP Controls if both were available?

As always, it depends...
If the VFP object or component does what I need, then I prefer to use it. It's native, generally faster and a lot easier to implement.

When would I use ActiveX? When there is no VFP equivalent (TreeView, DateTime Picker and assorted Calendar controls). Another reason might be when VFP lacks a certain functionality that an ActiveX supplies (some grids for example, or maybe some of the excellent BB controls from Bela Bodecs).

Another reason might be that you (or your client) wants a more "standard" Windows look. Some ActiveX may be needed so it will look exactly as another app they may have (maybe in VB or VC++). The look is similar cause you would use the same control. For example, you could GetDir() in VFP or you could use the ActiveX Common Dialog Controls for that standard look.

HTH