Re: How do I avoide multiple firing of confirmation code in OnBeforeDelete event?


>I noticed a recent post with the subject "Don't want to delete from
>secondary table".
>
>I was doing something similar and then read this post. I was not aware of
>the "UniqueTable" property. It works fine on my system. Cool. But there's a
>problem. If I select several rows in a grid and then hit the Delete key, my
>confirmation code in the OnBeforeDelete event fires once for each row that
>was selected. My previous code which was probably similar to Jon's did not
>have that problem because I was aborting during the OnBeforeDelete code.
>What's the best solution for this type of problem?

I assume you are setting a variable or property to indicate records can be
deleted? And you reset the variable in the BeforeDelete?
Just wait and rest that variable in the AfterDelete when there are no longer any
selected records
--
Brian Bushay (TeamB)
Bbushay@xxxxxxxxx
.