>> If you still feel the way you do, then go ahead and move over to VB/SQL.
>
>There is yet another insidious factor within the VFP vs VB issue, so far only tangentially mentioned. I want to first acknowledge that there are lots of excellent VB developers out there. However, on the other hand, my own observations have lead me to believe that VB is also kind of a "mediocrity magnet", and VFP -- by virtue of its barrier to entry to learn -- is not. VB is an ideal tool for entry-level programmers who can create simple apps. Likewise, IS managers who haven't written any code themselves in years also like VB (and there are lots of IS mangaers like this in corporate America) because it gives a sense of empowerment and being in control. What you have then is a group of people who have weak backgrounds in software technology --- i.e., couldn't write their own quicksort or infix-to-postfix routine if their job depended on it -- yet have a self-delusion of being experts in software development. The end result in a worst case scenario (which I have seen all too
>often) is a passive-agressive group of insecure folks who take a long time to do mediocre work, and are very resistant to change. The last thing these folks want is some VFP-slinging consultant to come in and show them up.
>
>I believe that a smart progammer can do awesome things with either VB or VFP. What troubles me is the politics of mediocrity that VB indisiously slips into the equation of IS decision-making.


The same has been said about Fox, but IMO it just doesn't apply to VFP. Fox DOS & Windows were so easy to develop. VFP took it to another level. The OOP capabilities took things to another level and only the serious took that step, even though it isn't required.