Hiya Rick ---

I agree 100%. In most corporate situations with a lot of forms and objects and where footprint is not a big deal, VFP whoops VB's ass in RAD and consistancy simply because it's more OOP oriented. I whipped up a VFP app one week to help a client: They decided to convert it to VB....it's been 6-7 weeks and they're still working on it :)


>I look at it this way: I use the tool that works best for the way
>I do development. I've been spending a fair amount of time with
>various other tools (VC++ and VB, but also Delphi and Borland C++)
>and I still continue to depend on VFP as my main platform.
>
>It's an excellent tool that is much better than all of the others
>for stable applications quickly. Most tools can do the same things
>it's just that in VFP most of them can be accomplished much more efficiently.
>The things that it doesn't do well can be rather easily expanded by using
>other tools to complement.
>
>Where does that leave you and me? For me, it means I'm not giving
>up on VFP. For somebody new reading this? They may want to think
>long and hard whether VFP is the right choice for them, because of this.
>
>As long as VFP is around, I'll keep on using it, but at the same time
>it's important to be familiar with what else is available, just in
>case <s>. If you know VFP well enough, you'll be hard pressed to
>find a worthy replacement...
>
>Also, consider of renaming yourself a Visual Studio developer and that
>may take off some of the 'bad' name that VFP has gotten for no
>reason in particular.
>
>+++ Rick ---