Gunnar --

Yeah, those things occur and you have alternatives.

For Michel, where he's trying to trap for occurences that happen more quickly than code can trap, using the data engine by forcing it to validate values thru a candidate key will ensure that no duplicates will be stored. So, if that's the best approach for him, there's a ready solution to address the "leakage."

Have a good weekend.


Jay

>hi Jay
>
>but then i have to switch between set deleted on/off. that looked to me like too much hassle. in the app i am working on currently records are beeing deleted by the users all the time. for this specific situation mostly out of stupidity from the user. because later they remember "duh, i needed that entry after all..."
>
>>This is easily resolved by SEEKing on the index expression of the candidate key and doing an UPDATE/REPLACE rather than an INSERT.
>>
>>Jay