Hi,

I was hoping that someone else would answer your question. I also thought your question would spawn more of a thread. I am taking night classes for UML and modelling and have a professor who is very biased against VFP and very pro VB. He explained to the class the following progression:

1) Junior programmers begin with tools like MS access
2) Then after learning the basics they move to a language like VFP
3) After mastering VFP they move onto the real language - VB.

Needless to say, I was though this was quite an amusing spin. Almost amusing as saying that VFP needs extra .DLLs so VB should be used instead. I assuming that you are talking about using VB on the front-end. In this scenario a VB app is more likely to use MORE external .DLL files than a VFP based app. VB has fewer built in controls than VFP and requires more external .DLL and .OCX files. This heart of the matter - cost of ownership and support. An HTML based front-end with any app-server is the only sain choice for internet/extranet applications. VB or VFP for a front-end in this type of apps will give you a lot of support headaches. If your core competancies are VFP then I suggest an HTML front and West-Wind Web Connection as the app server.

Peace
Jon