There is no uniqueness constraint. This field in the table already has duplicated values in it. It is not an identity field. I was trying a combination of things and could not get them to work (setting the value to zero, setting it to a positive value, including the field in the update and not including it, etc.). Technically, this field should not be in this table, but I didn't design it. I'm working with another programmer who did that. I decided that, for now and for testing, I'm just going to delete it from my copy of the SQL database. That got me around the problem for the moment. Hopefully I'll have time later to restore the database from backup and try again to figure out exactly why it was not working (especially if he doesn't remove this field himself).

Thanks for your reply.

>Do you have some kind of uniqueness constraint (not necessarily Identity)? Sounds like you are counting on SQL Server to auto-populate this column but have not defined a way for SQL Server to do so.
>
>>While attempting to use a CursorAdapter to talk to a MS SQL Server 2000 backend, I am getting a 1526 error that says "CommunityId column does not accept null values." It's a BIGINT data type on the back end and I have it set to zero in the record that's getting updated. And actually, I have that field now set to not update via the Auto-Updates tab in the CA builder, yet I still get this message.
>>
>>I needed to add six records in a VFP table to the SQL table. I was able to add the first record with no problems, but now I get this error. I'm not sure why it would work once and then wouldn't work after that.
>>
>>Any thoughts would be appreciated.
>>
>>Russell Campbell