Perry,

I think that the discussion may concern FREE tables.


>As I stated previously, and along with what Bob Archer stated, it is not the provider. You are not telling it to insert anything into the column, so it doesn't. However the NOT NULL designation on the column says you must insert something.
>
>As I stated before, you handle this issue on the database side by defining default values on any NOT NULL columns.
>
>Perry
>
>>I understand what NULL means. What I don't understand is why the OLE DB Provider for Visual FoxPro inserts a NULL into my field(s) if I don't specify that field it in my insert command? Let's say I have a table with 5 fields. In FoxPro, if I do an insert command for one of the fields (I.E. INSERT INTO mytable (myfield) VALUES ('mydata') the rest of the fields in the table are defaulted to whatever type they are. If I use the OLE DB Provider to Visual FoxPro with the same syntax, it inserts NULL values into the fields I do not specify. So my question, is there a setting that the OLE DB Provider has to turn of the NULL insert?