"...It would be better if you could tell SQL Server exactly what record to update using the record's primary key."

I'm only ever selecting one record at a time, for editing purposes, and therefore SQL knows explicitly which record is to be updated. The type of APP that I'm developing wouldn't have an instance where the user was editing multiple records at a time, hence I've not included this functionality in my code.

However, if this did change then I'd need only modify once piece of code, i.e. the routine that prepares the table for updates. That was my earlier concern in using only dynamic code rather than hard-coding. As we all know, in order to make some dynamic it takes considerably longer to write/test, however not only can it be reused but you also tend to find that it contains less bugs at run-time (as you've spent so much time developing it).

Regards

Derek