>BTW, is there any documentation or help file for the VFP OLE DB provider yet?

Umm, probably not. I know I wasn't asked to review anything specific to the provider that would ship with the beta, so I'd guess if there's nothing in the readme, then you're on your own.

>I did notice the default setting for SET ANSI is 'ON' and I believe SET DELETED was 'ON' by default also. What would be the appropriate way to change these environment setting if need be?

Similar to the ODBC driver, you should be able to issue Fox commands using the command object. For instance:

Local oCmd as "adodb.command"
oCmd = create("adodb.command")
*-- set ActiveConnection, bla, bla, bla
oCmd.CommandText = "set deleted off"
oCmd.Execute

> Also, I ran a test query against a table with an integer primary key e.g. "SELECT * FROM table WHERE table.pkey = 100" and it seemed as though a table scan was performed instead of using the Pkey INDEX.

How did you reach this conclusion? From what I've seen, this behavior should not be occurring.

> I don't suppose there's a way to view the optimization plan for a query ran through the OLE DB provider?

None that I know of, since the provider isn't going to like SYS(3054) very much.