[AccessD] BeforeUpdate v. AfterUpdate

The confusion was between Control AfterUpdate and Form AfterUpdate
events.

Charlotte Foust

-----Original Message-----
From: Mark Whittinghill [mailto:mwhittinghill at symphonyinfo.com] 
Sent: Tuesday, May 20, 2003 8:53 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] BeforeUpdate v. AfterUpdate


As Charlotte pointed out, I was thinking Control.OldValue.  Unless you
were also, in which case we're back to confusion.

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


> Interesting. I just did experiments and don't see how your stuff can 
> work. In AfterUpdate, I get OldValue = Value, invariably, and I've 
> done about 20 tests. I'm using debug.print to dump the values and in 
> BeforeUpdate they differ but in AfterUpdate they never differ.
>
> A.
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark
Whittinghill
> Sent: May 20, 2003 12:12 PM
> 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.
>
>
> _______________________________________________
> 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