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

My VB experience is very limited as well, but it seems VB6 would interact the best with your ActiveX controls. As you probably know, many ActiveX controls aren't tested with VFP, so mileage varies. Supposedly, VS .Net works well with ActiveX controls too, but I haven't tried it personally.

If you are looking for a learning experience, I would pick either VB6 or VS .Net. Otherwise, go with what you know. I think .Net is a good technology fully backed by Microsoft, and is worth learning about. However, IMO, that is not a compelling reason to stop using something that works for you now, especially an excellent tool like VFP.