Thank you all for posting about this.  I have been debugging this same issue today.  If this is expected behaviour, then in my opinion it should be documented in the help, and the SetItemStatus should return a -1 when the column status is not changed.  We don't use the Update() function to generate the insert SQL, but instead send all the fields to an 'insert' stored procedure.  I would like to set a column status to NotModified! after setting it to a default in a script with SetItem.  This way I can check if a user has modified any fields later with ModifiedCount().  I know setting the row status works in my case, but thought it would be generally more appropriate to change each column status immediately after each SetItem.

Hi Thorsten;

  Don't forget to set the Row Status other than NewModifed! for this to work. If that is not convenient for your App, you could also attack the problem with a Modify() to change the updatable columns. Thus, having the same effect on an Update().

Regards ... Chris

thanks, Rene,

I do want the Insert but I need the certain column to be Notmodified for further processing

I guess your row is new. In this case the SetItemStatus function doesn't changes the column status to NotModified! It seems not documented but logical behaviour because it uses all columns in the INSERT statement anyway. If you don't want to do the insert you have to change the row status.