>Here are the issues:
>
>1. VFP is the best database development tool MS has.
>2. The DBF file doesn't carry much weight in IT these days.
>3. MS would support VFP more if it sold more.
>4. MS would support VFP more if it helped them sell more NT licences.
>
>Here is the solution:
>
>1. Don't buy VS (VFP usage is hidden from MS).
>2. Buy 2 copies of VFP 6.0 (one new licence, one upgrade).
>3. Write to MS requesting full ActiveX support.
>4. Write to MS requesting a SQL Server engine as well as a DBF one.
>5. Write to MS every month of the year. Every month without fail.
>
>Here's the result:
>
>1. MS will market VFP more 'cause sales are increasing.
>2. MS will commit to VFP 8.0 which will be VB with VFP database tools.
>3. We'll be happy 'cause we'll have VFP for the next 5 years.
>
>And as we all know, 5 years in the IT industry is a VERY long time.
>
>David Turnedge.


Here's the facts:

1. We need multiple tools these days. VFP alone will not do it. As John stated, this will further show that VFP developers are in an island.

2. Will you please purchase the other tools that I need and send them to me?

3. What is full ActiveX support? VFP complies with the published ActiveX standards.

4. You can already get to SQL Server.

5. Pretty soon, Microsoft will see your letter and just stop listening.