In addition to the answers you've received, the problem may be that your view doesn't contain all the fields from the backend table(s). If this is the case, then the backend will fill the missing fields with .null. values.

You have several options to work around this problem:

Define default field values on your backend table(s). In this case, the backend will use the default values rather than null.

However, if this is not possible you need to find a solution within VFP. You could define your view as SELECT * and make all fields updateable.

Then you need to explicitly pass values for each field in your INSERT INTO statement using "empty" values as mentioned by Evan for fields you don't want to update.

Another approach which may be easier to code is:

APPEND BLANK
BLANK
REPLACE MyField1 WITH MyVal1,;
        etc.

HTH

>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?