First, why is the user allowed to edit a unique key field? I would prohibit that entirely which would stop the error from possibly occuring. Second, in addition to Yuri's comments, have you tried changing the default update method from 'SQL DELETE then INSERT' to 'SQL UPDATE'? Just a thought.
Tracy
>Tracy:
>
>You understood OK. I throw the error routine but, what's the appropriate code anyway?. The real question is: Can I recall a deleted record in a table from a view? (I'm working strictly in a view).
>
>
>mandy
>
>
>>Doesn't it throw the error to your error routine when this happens? Can you trap for the error 1884 in your error routine and if the error matches, run the appropriate code? Maybe I'm not understanding correctly...
>
>>Tracy
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
