Form Events

[David C. Holley]

Could someone please refresh my memory as to the sequence that the
follwoing events are fired when a new record is added?

AfterInsert
AfterUpdate

David H

 

[Karl E. Peterson]

Could someone please refresh my memory as to the sequence that the
follwoing events are fired when a new record is added?

AfterInsert
AfterUpdate

The easiest way (certainly quicker than posting here!) to determine event order is
with Debug.Print statements. Give it a try.

 

[Dian Chapman, MVP, MOS]

Further to Karl's advice, you might want to check out this TechTrax
article for details...

Office VBA-Basic Debugging Techniques
http://pubs.logicalexpressions.com/Pub0009/LPMArticle.asp?ID=410

Dian D. Chapman, Technical Consultant
Microsoft MVP, MOS Certified
Editor/TechTrax Ezine

Free Tutorials: http://www.mousetrax.com/techtrax
Free Word eBook: www.mousetrax.com/books.html
Optimize your business docs: www.mousetrax.com/consulting
Learn VBA the easy way: www.mousetrax.com/techcourses.html

 

[David C. Holley]

Actually, I went stricktly with the afterUpdate event. I'm implementing
code that automatically creates & updates Outlook appointments. The
initial idea was to use createOutlookAppointment() on AfterInsert
function and then use updateOutlookAppointment() on AfterUpdate. I'm now
testing if the Appointment has been created and calling the appropriate
function. createOutlookAppointment() captures the EntryId and stores it
in the Access DB for use by updateOutlookAppointment() so if the EntryId
doesn't exist, we need to create the appointment.

David H