Yes, that would be correct. In this case, the requirements were to show a Field History, and if someone is changing the value in a column, and then perhaps changing it back to its original value during the same edit process, then the column has been updated, even though the value may not change. So, you're correct in saying that the former and current values are not compared. We simply know that the column has been updated.

The aim of this script was to avoid saving an entire row from the table, which some triggers do and is much easier, merely because one column may have been changed. In that case, a "Field History" would have shown multiple instances of the same value, even though that column wasn't even touched.

One very expensive alternative would have been to add a Last Modified timestamp associated with every column, but the main table in this application is approaching 100 columns, and the overhead was considered too extreme.

Thanks for your comment!

Larry