Kev,

>>No, you've been most helpul, thanks.

You're welcome, I try ... <g>

I usually allow NULLs in all columns in a table except the PK and possibly a few FKs. I realize there are business reasons for not having a particular column contain NULLs, but where at all possible I let NULLs happen.

~~Bonnie


>>Kev,
>>
>>>>I hope there is a way of excluding NULLS being placed into the fields from VB, rather than having to change my VFP table?
>>
>>Yes, I'm sure there is, but VB isn't my strong point. Plus, I'm not using the da.Update() to update my backend (we use SQL Server and SPs), so I'm afraid off the top of my head I can't point you in the right direction, other than to say that it's something you'd need to set in the DataSet I think. Either that or, if there's not that many NON-NULLable columns, just make sure you set them to something before you update ... after all, they shouldn't be NULL to begin with.
>
>Yes, there aren't 100's of fields, so I will ensure they are blanked/filled.
>
>>(I know, I'm not much help today ... need more coffee!! <g>)
>
>No, you've been most helpul, thanks.
>
>Kev
>>
>>~~Bonnie
>>
>>
>>>>Kev,
>>>>
>>>>My guess is something in your table that doesn't allow NULLs ...
>>>>
>>>>~~Bonnie
>>>
>>>Yep, just after I sent this message (typical!) I tried the same call from VFP through ADO and that gave me the meaningful message I was looking for.
>>>
>>>I hope there is a way of excluding NULLS being placed into the fields from VB, rather than having to change my VFP table?
>>>
>>>Thanks
>>>Kev
>>>>