>>>>2. Make training available. Quit restricting VFP training to MS owned Unervisities in the orient. Make CBT training available in the US.
>>>
>>>They've tried that. Remember "Mastering Visual FoxPro"? It didn't sell.
>>
>>That could be because it sucked. It was an exact rehash of the docs that shipped with VFP 5.0. If something sucks, it doesn't take long for word to get out.
>
>Hi Erik, this isn't directed toward you, it's directed to everyone in this thread.
>
>Microsoft isn't interested in advertising Foxpro. Microsoft wants everyone needing development tools and databases to buy SQL Server and Visual Studio.
>
>If people are not aware of Foxpro's power, then they will buy what Microsoft recommends, which is Visual Studio and SQL Server, namely Visual Basic and SQL Server. It seems that Microsoft views Foxpro as a product that satisfies a niche market. Microsoft probably will never put alot of marketing behind Foxpro as long as SQL Server is in the forefront. Just think of all the companies who have bought SQL Server who really don't need it.


Or worse still, just think of all the companies that use/switch to Oracle and could really benefit from SQL Server! Especially since many of these hapless organizations think they can do this without a DBA!

I think the real battle is the database server market, not VFP vs. VB or VS. We're all in the same boat as MS developers, trust me. We should be leveraging for SQL Server and Visual Studio getting more market share for the enterprise instead of carrying on about VFP (which will always be around and will always be less than popular).

I'm looking forward to .NET and hope it becomes as popular and easy to learn as VB & ASP so I don't have to switch to such dreadful technologies as C++ or Java or Oracle. Ewww. I'm kind of bummed about Visual InterDev going away though. That has more of an impact on me than VFP marketing coverage.