Kevin,

I wrote:
>When saving data to a VFP table, I am getting the following error: "OleDbCommand.Prepare method requires all parameters to have an explicitly set type."

You wrote:
>I'm curious...if you remove your business object project and use the sample application's business object project instead does it work properly?

I used the sample application's business object project as you suggested and I was able to edit the VFP tables without any run-time errors. The only errors/bugs I ran into were:

1. web.config - the connection string was still pointing to the 2003 sample folder instead of the new 2005 folder.
2. OrderEdit Web Form - when trying to add the BindingSourceMember to the testboxes, I keep getting an error message that says: "Object reference not set to an instance of an object." . I get this as soon as I click on the elipses button. I am able to use the elipses to select the BindingSource and if I enter the field names mannually the web form works fine. That tells me (I would think) that my connection string in the web.config file is ok. Any ideas on this?

Now that I can get the Northwind data to work, are there any special requirements for setting up a VFP DBC file. The DBC and tables I am getting my errors in are part of an accounting system called "SBT ProSeries". I don't know if you are familiar with that one but it uses a standard VFP DBC file and tables. The main difference is that the tables, in their native form, do not have a primary key setup. I added the primary key field and index when I started building this web app.

Also, I did find that updating my VFP OleDb Driver to the one release with VFP 9.0 helped too.

If you need any other information to help me get pass this, please let me know.

Thanks again ...