>>>I think we can't blame Microsoft (or Ken) for their approach to market VFP and the "secrecy" of their plans. We are VFP developers, know it and like it (a lot); that's all we care and we think such a product deserves more attention from Microsoft.
>>
>>We're not blaming them for what they're doing. We're blaming them for what they're not doing ;-)
>
>Dear Denis,
>if you read carefully my post you'll notice that it's addressing why they don't do that much on the marketing side. Of course it's only my guess, and I might be completely wrong.

Ok then this must mean that they made an error buying it in the first place if they did'nt have a place for it.

This is what I and many others think about that non-marketing situation.

Access does'nt work well with many records.
VB is not a data-centric development language.

VFP is very good with many records and it's a data-centric development environment. So right there MS had a very insteresting solution. But the problem is that this solution is so good that it could affect SQL Server sales. A lot of businesses don't need SQL Server but still MS is there to make money so instead of telling their customers to go to VFP they're pushing SQL Server as hard as they can.

In the process they'll lose some customers to VFP. That is those that already know that VFP can do the job they need but many others never heard or don't trust VFP because of the lack of marketing.

So to me that explains the non-marketing efforts on VFP.