D
Daryl
Hi all
It appears Access2000 project has a small problem with the timing of the
following events to their actions.
Private Sub Form_Delete(Cancel As Integer)
Private Sub Form_BeforeDelConfirm(Cancel As Integer, Response As Integer)
Private Sub Form_AfterDelConfirm(Status As Integer)
Private Sub Form_Delete(Cancel As Integer)
' Update the values in the list-box to reflect the change in hours worked
Me.Parent.lstAllocatedTasks.Requery
End Sub
It appears that if you use the Delete event to requery a recordsource that
say does a recalculation on the records that you just deleted one off
therefore the change should be reflected in the result but it is not.
However if you delete another record then the change of the previous delete
is reflected in the result.
This indicates to me that the Delete event is firing directly after the
based on the AfterDelConfirm event (in my case) but it is before the actual
delete occurs on the data. Therefore, I do not see the change until the net
delete.
Could someone please confirm this is an issue with MS Access2000 when using
projects (adp) and is there a workaround.
Thanks
daryl
Microsoft Knowledge Base Article - 234866
When you delete records in a form in a Microsoft Access project (.adp), the
order of events is different than when you delete records in a form in a
Microsoft Access database (.mdb).
In a Microsoft Access project, the order of events when you delete records
in a bound form is as follows:
BeforeDelConfirm-->AfterDelConfirm-->Delete
In a Microsoft Access database, the order of events when you delete records
in a bound form is as follows:
Delete-->BeforeDelConfirm-->AfterDelConfirm
It appears Access2000 project has a small problem with the timing of the
following events to their actions.
Private Sub Form_Delete(Cancel As Integer)
Private Sub Form_BeforeDelConfirm(Cancel As Integer, Response As Integer)
Private Sub Form_AfterDelConfirm(Status As Integer)
Private Sub Form_Delete(Cancel As Integer)
' Update the values in the list-box to reflect the change in hours worked
Me.Parent.lstAllocatedTasks.Requery
End Sub
It appears that if you use the Delete event to requery a recordsource that
say does a recalculation on the records that you just deleted one off
therefore the change should be reflected in the result but it is not.
However if you delete another record then the change of the previous delete
is reflected in the result.
This indicates to me that the Delete event is firing directly after the
based on the AfterDelConfirm event (in my case) but it is before the actual
delete occurs on the data. Therefore, I do not see the change until the net
delete.
Could someone please confirm this is an issue with MS Access2000 when using
projects (adp) and is there a workaround.
Thanks
daryl
Microsoft Knowledge Base Article - 234866
When you delete records in a form in a Microsoft Access project (.adp), the
order of events is different than when you delete records in a form in a
Microsoft Access database (.mdb).
In a Microsoft Access project, the order of events when you delete records
in a bound form is as follows:
BeforeDelConfirm-->AfterDelConfirm-->Delete
In a Microsoft Access database, the order of events when you delete records
in a bound form is as follows:
Delete-->BeforeDelConfirm-->AfterDelConfirm