I wish I could, but I don't have a copy of VFP8 on either my local machine or the server. What I wound up doing was create a stored procedure that will tell ASP.NET what the next valid number is, then just stuff the record with that value in the insert statement. It works, but still is perplexing why the OLE provider doesn't seem to respect default value clauses.

thanks for the idea.


>Hi Steve,
>
>I don't know if it makes any difference, but did you try the latest version of VFP OLE DB provider that comes with VFP8?
>
>>I have a VFP 7 DBC setup with a stored procedure that provides an autoincrement function. From within VFP, if I open the table and insert a record, either by ctrl+y or using the insert command, the key field displays the next available id correctly. (I have a primary index based upon the value as well).
>>
>>However, if I open the table from ASP.NET using OLE and attempt to insert a record, I get "Index does not accept NULL" error message. I have null values enabled for every field in the table, but the message still happens. Currently, editing a record through ASP.NET & ADO is no problem; only inserts. Is this something with the nature of the VFP ADO driver or something else? How can I get an autoincrement to work via ADO?
>>
>>My thanks to any suggestions!