[AccessD] BeforeUpdate v. AfterUpdate

Ahh... I missed the part about form AfterUpdate

Mark Whittinghill
Symphony Information Services
612-333-1311
mwhittinghill at symphonyinfo.com
----- Original Message ----- 
From: "Charlotte Foust" <cfoust at infostatsystems.com>
To: <accessd at databaseadvisors.com>
Sent: Tuesday, May 20, 2003 9:33 AM
Subject: RE: [AccessD] BeforeUpdate v. AfterUpdate


> You can't use it after the *form's* AfterUpdate event because at that
> point all the OldValues are the same as the current value.  You're OK
> with the control's AfterUpdate event because the data hasn't actually
> been written to the table yet.
> 
> Charlotte Foust
> 
> -----Original Message-----
> From: Mark Whittinghill [mailto:mwhittinghill at symphonyinfo.com] 
> Sent: Tuesday, May 20, 2003 8:12 AM
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] BeforeUpdate v. AfterUpdate
> 
> 
> That's interesting, because I use OldValue with AfterUpdate all the
> time, and it works just fine.
> 
> Mark Whittinghill
> Symphony Information Services
> 612-333-1311
> mwhittinghill at symphonyinfo.com
> ----- Original Message -----
> From: "John Colby" <jcolby at colbyconsulting.com>
> To: <accessd at databaseadvisors.com>
> Sent: Tuesday, May 20, 2003 7:39 AM
> Subject: RE: [AccessD] BeforeUpdate v. AfterUpdate
> 
> 
> > OldValue is set to Value when the data stores, thus by AfterUpdate the
> 
> > OldValue data has indeed been lost.  Use BeforeUpdate to store the 
> > value
> to
> > a variable, then compare to that variable in AfterUpdate.
> >
> > John W. Colby
> > www.colbyconsulting.com
> >
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Arthur 
> > Fuller
> > Sent: Tuesday, May 20, 2003 9:29 AM
> > To: AccessD
> > Subject: [AccessD] BeforeUpdate v. AfterUpdate
> >
> >
> > >From my experiments, it appears that MyControl.OldValue is available 
> > >for
> > scrutiny only in the BeforeUpdate event. In the AfterUpdate event it 
> > seems to be lost. I just wanted to confirm this hypothesis.
> >
> > The point of the exercise is that I need to keep track of which 
> > columns a user has changed and then take action accordingly. I have to
> 
> > update some columns in another table depending on which columns 
> > changed in the current table, but only if the update to the current 
> > table was successul. I don't actually care about the old value, I'm 
> > just using it to determine which columns changed. But by the time I 
> > get to AfterUpdate I've lost the information.
> >
> > Any suggestions as to how to work around this?
> >
> > TIA,
> > Arthur
> >
> > _______________________________________________
> > AccessD mailing list
> > AccessD at databaseadvisors.com 
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> >
> >
> > _______________________________________________
> > AccessD mailing list
> > AccessD at databaseadvisors.com 
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> >
> 
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
>