Re: How do I avoide multiple firing of confirmation code in OnBeforeDelete event?
- From: "Keith G Hicks" <krh@xxxxxxxxxxx>
- Date: Mon, 27 Jun 2005 16:41:43 -0400
Yes. Thank you. That is what I was attempting to do. I just didn't take it
to the next step of counting how many rows are left to delete. It didn't
occur to me at first that the grid is sending the delete statement to the
TAdoDataSet one row at a time. I'll give this a shot although I like doing
the delete manually via a stored procedure. I feel like I have a bit more
control that way. Just my funny way of thinking maybe. :-)
Keith
"Brian Bushay TeamB" <BBushay@xxxxxxxxx> wrote in message
news:5bqub1tia23sm43k26913m62687m4jjcrj@xxxxxxxxxx
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
.
- References:
- How do I avoide multiple firing of confirmation code in OnBeforeDelete event?
- From: Keith G Hicks
- Re: How do I avoide multiple firing of confirmation code in OnBeforeDelete event?
- From: Brian Bushay TeamB
- How do I avoide multiple firing of confirmation code in OnBeforeDelete event?
- Prev by Date: Re: Internal Query processor Error
- Next by Date: Re: Not A Valid Password
- Previous by thread: Re: How do I avoide multiple firing of confirmation code in OnBeforeDelete event?
- Next by thread: Not A Valid Password
- Index(es):