Hi Kevin,

>>
If you are getting the primary key value from sql*server and using the @@ command to retrieve it, beware that if you have insert/update triggers that create records in other tables (like audit tracking) then this could give you the those table's ID values instead (ok -- I only read about this on UT, I am still setting the primary key from a last used id table)
<<

Thanks for the info. Am not doing anything fancy like that. But I just figured it out (I think)!!

I was appending to the remote view from a cursor (Append From DBF("cursorname")). The cursor had an ID number field and the operation was trying to populate the view's ID field w/ it's value. That was causing something to go amuk (even though that ID number wasn't in the view). So, I just changed to an Append Blank and a bunch of Replace commands and so far, so good!

Thanks,

-paul