>Mike,
>
>>I didn't put words into your mouth. I said free Database product, not free VFP7. If you give free access to a database that is freely distributable, you now how a completely free database (the FoxPro database) available that is competeing with your flagship database (SQL Server). THAT is bad marketing.
>
>According to your premise, MSDE is also bad marketing... Do you agree?
>
>>Your drawing this parrallel to the VFP and SQL oledb providers but your completely over looking the databases themselves. A free SQL provider leads to expensive SQL licenses...
>
>Except when used with MSDE.
>
>>...A free FoxPro provider leads to... lost revenues.
>
>How does anyone KNOW that a free provider leads to lost revenue? I just don't see where the loss is.
>
>Are you suggesting that lost SQL Server revenues is the basis for Microsoft's decision about the VFP OLE DB driver?

I think there is a fundamental "failure to communicate" here. And it may stem from some contradictary information in the documentation.

Under the topic OLE DB Provider for Visual FoxPro, it states:

Create and maintain database containers (DBCs) through extended Data Manipulation Language (DML) functionality and ADOX enhancements to ADO.

If this true then, you can get all the benefits and power of VFP without buying anything. This isn't simply access. It is creation. With the SQL Server and Access providers, you can't create databases and file-based MDBs. You can only access them.

Having said that, under the topic Unsupported Visual FoxPro Commands and Functions, it states CREATE DATABASE is not supported.

One of these statements is wrong. Which one is correct is the determining factor in whether I want the VFP provider distributed via MDAC.