>This is a quote from Steve McGrath's blog he shared with me yesterday:
>
>Taken from my blog:
>
>"The markets are not the same. Most applications in Visual FoxPro are for business and for non-profit organizations. VB main focus was not on database development. The impact is very different here. Also, Linux is becoming more widely available than 5 year ago(start of .NET) and some of those business may go that way so not to get burned. Microsoft is forgetting the secondary revenues that FoxPro gives them by keeping them in the Windows world. In a few years, Linux will be a real competitor to Windows when more ordinary people start to install it on their desktop."
>
>Absolute hogwash! He already said he has no knowledge of VB, but it doesn't stop him from talking about it. He works for a non-profit, so he thinks he is able to qualify VFP as a development tool for non-profits too. I have friends in the non-profit industry. Most use Access.

You say that I have no knowledge about VB. It's true and I already responded to that in the other thread. But don't thing I only worked with Fox. I did some assembler, binary programming, Pascal, Cobol, Basic, C ...and now FoxPro, VFP. It's not because I don't know a language(your VB) that I can't make an analysis of it. All languages can do databases and it's just a matter of how well it does it and does it fit the clients needs.

But do you have "real" knowledge about non-profits(small and mid size) or is it just from your friends? Red cross does not have the same needs than a local one.
Did I ever said that VFP is the best for all solutions? No.
Can Access be good for a non-profit? Yes.
Is it because it came bundle with Office?
Did your friends know FoxPro existed?
Would they had to pay extra for it?

In my quote, I said that 5 years ago it was the case. Don't blame me if the marketing was bad in selling VBNet also to the database crowd. Maybe, they just targeted the North American English markets back then. I don't know. They did not sell VFP better. ;)

Where I used to work(the non-profit), we were exploring what to use when passing from FoxPro Dos to Windows. We looked at many options(Windev, VB ...) from a database point of view and the needs of our clients. That was 1 year before the .NET. It was too late to turn back. We took VFP and it is a multi year on going project. My former "boss", in the non-profit, were small towns(1000-2000 residents) where the budget is very tiny and not waisted. Just making them buying a new computer was not very easy in most towns. You see the kind of restriction I had to deal with.

My issue is not with new projects but with existing projects on the long run.