>and you think that it got that way on it's own? sorry to have to p** in your post toasties, but it actually got that way from the countless millions MS hurled at it!


I think that is what frustrates alot of us (me for sure). Somebody else earlier in this thread said something to the effect that the 'whining' should stop and we should accept things the way they are. I do accept that VFP appears to be the ugly stepchild in the Microsoft Development family (my perception only) - and that this will most likely remain the case. That doesn't mean that I'm happy about and it certainly doesn't mean that I won't vent my frustrations once in a while ... I'm so ******* tired of hearing that Access is the best tool to use when developing desktop/network apps with. Just as tired as I am when I utter the letters V-F-P and look at the blank faces that stare back at me.

Access-VB-SQL are different from VFP - not necessarily better or worse. Each of the tools has it's strenghts/weaknesses - including VFP. I personally like working with VB6 - but for the type of systems I develop, VFP is the best tool for most projects.

The reason VFP has such lousy reputation (i.e. very few people other than those of us who use it and know how great a tool it is) is directly related to it being the blacksheep of the MS Suite of development tools. And because of VFP's blacksheep status - the relative $$$ spent on advertising is probably less than 1% (my guess) of the VB advertising budget. No matter how good a product it, people won't buy it if the never hear about it.

Would VFP be more widely used if MS had equally divided the advertising budget between VB-Access-SQL-VFP four or five years ago and continued that approach. My guess it that it would.