G
Guest
Hi,
I'm running a copy of Access 2003 and I was doing some reading and testing
(breaks in code) on the firing order of the Delete, BeforeDelConfirm, and
AfterDelConfirm events. And to my suprise the results do not match what is
described in the Access Help.
Here are the results:
The first time a form opens and I initiate a delete (i.e. by pressing
CTRL+[-] or selecting the record and pressing DEL), the Delete event occurs,
but the BeforeDelConfirm and AfterDelConfirm events do not. I'm not even
prompted as to whether I want to delete the record.
When I try to delete a second record then the event sequence changes. First
the BeforeDelConfirm event occurs, followed by the AfterDelConfirm event, and
finally the Delete event.
From what I've gathered from the Help, the Delete event is supposed to occur
first, followed by the BeforeDelConfirm and AfterDelConfirm events. But as
you can see this is not the result that I'm getting.
Does anyone know if this is a know issue? Or, is fixed by a possible service
pack?
I can't find any related problems on the Internet.
Any help is greatly appreciated.
Thanks,
Andrew
I'm running a copy of Access 2003 and I was doing some reading and testing
(breaks in code) on the firing order of the Delete, BeforeDelConfirm, and
AfterDelConfirm events. And to my suprise the results do not match what is
described in the Access Help.
Here are the results:
The first time a form opens and I initiate a delete (i.e. by pressing
CTRL+[-] or selecting the record and pressing DEL), the Delete event occurs,
but the BeforeDelConfirm and AfterDelConfirm events do not. I'm not even
prompted as to whether I want to delete the record.
When I try to delete a second record then the event sequence changes. First
the BeforeDelConfirm event occurs, followed by the AfterDelConfirm event, and
finally the Delete event.
From what I've gathered from the Help, the Delete event is supposed to occur
first, followed by the BeforeDelConfirm and AfterDelConfirm events. But as
you can see this is not the result that I'm getting.
Does anyone know if this is a know issue? Or, is fixed by a possible service
pack?
I can't find any related problems on the Internet.
Any help is greatly appreciated.
Thanks,
Andrew