Hi Ricardo, actually they're just VFP tables, I'm connecting to them through ODBC, I'm sticking with the dummy field for now, I checked the accept null values option for it to avoid the error, but you're right it's more an issue with the base tables than what I can do from this end.

I hadn't thought of giving default values to the base tables, only tried to define default values for the view fields, but that didn't work; still just allowing null values seems like a better idea, thanks.

>Hi Jorge,
>
>I assume you're using SQL Server!
>The error VFP is giving to you cannot be solved with SET NULL ..., because the problem becomes from SQL Server. You must "uncheck" the ALLOW NULLS column at all fields of your table (by the way, give always a DEFAULT value too). It sounds terrible "unchecking" for all fields, but you can do it by code, when you are creating your table.
>Like you can check the UPDATABLE column at the creation of your views (use DBSETPROP()).
>
>Say anything if you need.
>
>Good luck,
>
>Ricardo