>I've got a weird situation. Our Internal Affaris bureau has a routine that was written by someone else that is supposed to pull all MPD Employee data from an Oracle database. That works. The data is pulled into a free standing table, then each record is checked against the employees table in a SQL Server (2005) using a parameterized remote view. If the employee isn't found, the record is inserted into the SQL table. The error message I get says the SQL table does not allow nulls in the "identity_column" column. Checking the record in the remote view, the data is there and is the correct data type (integer). Thinking the table might have been corrupted, I scripted it, exported the data to a csv file, pulled it into VFP checked for nulls and dups and found none, then dropped and rebuilt the table and imported the csv file back. Still getting the same fubar.

I "identity_column" column marked as updatable in the view?