Gustav Brock
gustav at cactus.dk
Fri Mar 5 06:49:46 CST 2004
Hi Sander Because doing anything in the BeforeUpdate event which has influence on the current record - like navigation on the form - usually will cause troubles if not failure. In my experience, this event should be reserved for validation or user confirmation - eventually setting Cancel to True. I guess that if you remove this naughty code line: frmKAM_ProcessKey (vbKeyPageDown) you will receive no error. /gustav > Gustav, > I was going to say No, it should be in BeforeUpdate but since you answered most of my questions on this list correct...why do you think it should be in the AfterUpdate event? > The code checks if there where any changes made to the current record. If so these need to be saved, or not. > I believe that who-ever programmed the app was correct in putting the code in the BeforeUpdate event. > Sander > Gustav Brock <gustav at cactus.dk> wrote: > Hi Sander > It looks like your action should be moved to the AfterUpdate event. > /gustav >> I'm using Access 2000 and I get an error 2105 when Access "leaves" >> the BeforeUpdate event. ..