Hi William,

Without some specific code and further information about what back-end database you're creating the remote view to look at, it's somewhat difficult to determine exactly what is causing this...but my initial thoughts are:

1) Logical fields -- sometimes they need a 1 or 0 and not a .T. or .F.
2) Character fields -- sometimes if the value you insert is too long for the field on the database, it shows up as null.
3) Numeric fields -- are you sending a non-integer to an integer field, or is the integer value too big for the datatype on the back end?

>I have set up a remote view and set it's cursor properties. I do an insert into the table.
> When I do a tableupdate() I get an .F. . aerror() tells me that a field will not accept null values. This is correct because the field is set up to not receive null values.
> The problem is I am not passing a null value. Does anyone know why SQL is seeing a null value when I am not passing a null value through the remote view?