FWIW I tried a different approach, simply comparing the value in the cursor with the value in the recordset, since modifications to such fields are already blocked at UI level, the value will not change, and thus my code won't try to update it, so that particular problem is solved. I just wish there was a way to determine such a thing in a more precise manner, but then again I suppose this is more an issue with the SQL provider than with ADO in general, thanks.

>>The reason I mentioned an identity (which is not a datatype, AFAIK) field
>
>You are right on this one. With SQL server, an identity field is numeric (int or other) than have a identity attribute.
>
>Don't forget that ADO is not built to access only SQL server and other database are not the same (ie, in Access you have an AutoNumber datatype).