>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!
>
>For what its worth, I'm not knocking VFP as the most powerful relational database tool available. I'm just shocked and pleasantly surprised by what I've seen in the non-VFP world. I have no reason to be biased towards one or the other; if anything, the time I've invested in VFP should bias me to VFP!

There are many things involved in development other than getting the application up and running.

- How do you handle modifications? My boss told me today that he wanted changes to the time entry text boxes I changed the class, recompiled....DONE! It would have taken MUCH longer in VB.

- How about multi-developer projects? We had an employee from Intersolv (the company that makes PVCS) in our office last fall. He had never seen VFP, but remarked that it had the best source code control interface he'd ever seen...better than VB, Delphi...and much better than PowerBuilder.

These things and others are often overlooked in the rush to get applications out the door, but should be considered in making decisions about development tools.