Depending upon the data types passed from the ActiveX components, you may need to use either VB or a VFP/VB combo. If it's not data-intensive, VB would probably work just fine - and it'll give you an excuse to broaden your skills, eh?

>I have been assigned the task of creating a new application. My experience is with VFP and I am partial to this environment. Are there compelling reasons for developing (or not developing) in VFP, as opposed to Visual Basic?
>
>Of course I like the integrated data functionality and rapid development that VFP has. A couple of issues that trouble me with VFP is that 1) it has been detached from the .NET framework, and 2) I seem to have troubles finding experienced VFP programmers.
>
>The application is not especially data-intensive; it will be used to drive a robotic cutting system. The robotic control functions have already been developed as VB Com objects and ActiveX objects. I don't think (I haven't seen them yet) that the ActiveX objects are data-bound (I've had problems in the past with this).
>
>I know this isn't much, but any input is appreciated as I have had very limited experience with VB. Thanks in advance.