>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.
In VB, you could create a custom "User Control". Changes to this control are propagated throughout your project. I find this also helps alleviate some of the dependancy tensions caused by multi-class components.
>- 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.
VB and VC++ are designed to work at a very high degree with MS Visual SourceSafe, the best project management tool I've seen so far. Also, the code editing environment is nothing short of phenomenal.
>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.
Believe me, myself, and the president of our company have considered these things long and hard. We may not have attacked all angles (yet), but the more we looked, the more suprised we have become. Out of curiosity, what source code control interface were you referring to? If you're speaking off-the-shelf VFP, there basically is none.