Thanks Doug,

The view is being refreshed, but I guess what's missing is a refresh of the form, so that all of the old values are redisplayed.

I guess this could be added to ErrorUpdateConflict(), so I'll give that a try. Also, in order to keep within the n-tier rules, I guess it would have to go on the BizObj that was dropped on the form, as opposed to the actual middle-layer BizObj.

The other issue is that when the user selects 'No', there really isn't any other option for them other than to press 'Cancel', since pressing 'Save' starts the whole update conflict cycle again. Perhaps the error message needs some user friendly reworking.

Kevin - framework enhancements????

Thanks for the help.