[AccessD] BeforeUpdate v. AfterUpdate

How about a 'changed column' collection populated in the BeforeUpdate
event of each control.  Then you can walk through the collection at the
appropriate moment.

Neal Kling
Lotus, isn't that some kind of fancy flower?


-----Original Message-----
From: Arthur Fuller [mailto:artful at rogers.com]
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