Hi Mike,

Sorry to email you directly, but I read some of your posts and you might be able to shed some light on my troubles.

I have been a longtime FoxBase\FoxPro\Vfp developer (along with c\c++\vb). I have been assigned to take some of my projects and move them into dotnet. The DBF's have to remain unaltered since the DOS FoxPro code still needs to work.

My issue basically is the lack of Schema information in the VFP OleDb driver for VFP7\8 (beta). Without this Schema info apparently ADO.NET cannot identify the primary keys, and won't generate the Update and Insert SQL code for the command builder to modify the tables.

I never expected the schema to identify the primary key, It can't since NDX and CDX's in the old days dont identify primary, primary is Recno() and everything else is a collating sequence Unique or not. I did expect that if I was to set the Primary Key in the DataAdapter, that the command builder would know what to do.

Do you know what changes if any we might see in the final release of the VFP8 OleDB driver? The incompatibilities in this driver could double the amount of work needed to port my project forward. I don't mind doing the work, I just don’t want to find out in 3 months that it was all for nothing.

Thanks,
Mike Pisano
Concordia International
Mpisano@ConcordiaFreight.com
(516) 561-1100