>>Then it seems that verifying the alias before the save would suit best?
>
>Tracy,
>
>I found this error message to be completely misleading and not helpful at all. In fact, one of the fields in the table was a foreign key. This field was not populated properly, so the Inser trigger should complain. However, instead of seeing the right message, I see "Record is not locked" message. So, it took longer to debug the problem.
So, it could be a trigger problem. Today we got this error in production. I can not reproduce the problem in our IT Testing. I may try to follow your advice to make sure the proper alias is selected. This particular error seems to be very hard to find the actual cause...
If it's not broken, fix it until it is.
My Blog