>You're absolutely right about personal preference. I do believe, however, the fact that I have been working with VFP for two years, and VB for two weeks, and that I can perform at almost the same speed in both, should have some bearing on the matter. One could argue that I'm just genetically predisposed <g> to VB development. On the other, it could be that the tools are more mature and make it easier for the developer. I cannot speak for Microsoft, of course, but it would be my place to recommend the most cost-effective solution to a problem to management in my company. If I could meet more deadlines using a different tool, so be it!
>

This has been a very interesting discussion I have been following, but it has proven one single thing only - you like VB over VFP. I say good on you, you've found your niche. I personally think that after you have had a little more than two weeks with VB, you may find it restricting too.

I have been programming in Pascal since 1982 and Delphi since about 6 months before the release of Delphi 1. Hell, I was even a Borland Consultant for a little while. I personally prefer VFP for the work I'm doing even though VFP contains restrictions - actually VFP has quietly had many things that are considered "new and amazing" in Delphi 3. If I work with the restrictions in mind, then I can get a lot of work done in VFP with more maintainable and updatable code - and the user is happy. I couldn't believe the excellence of the Object implementation in VFP, even though I think that it could do with more work (roll on Tahoe).

I have programmed in FoxPro since about 1991 and dBase before that so I'm not new to Fox, only VFP.

Go with VB if you are more productive in it, I can't stand it but that's what personal preference is all about. <smile>

Steve