[AccessD] Form Before Update

Francisco Tapia fhtapia at gmail.com
Thu Sep 1 16:14:27 CDT 2005


For the record, this is why I hate bound forms ;)...

the only reason I'm using it this way is because it's a data entry screen, 
and it can hold on to data if the connection were to be severed, this has 
happend to me because our of our NOTwork.. :(


On 9/1/05, Charlotte Foust <cfoust at infostatsystems.com> wrote:
> 
> If you have changed the control then the value in it should be whatever
> you changed it to, assuming the AfterUpdate of the control has actually
> occurred. The previous value will be in the OldValue property until the
> Form's AfterUpdate event occurs. The text property of a control is only
> available when the control has the focus, so it won't be available from
> the command button. Button clicks can intervene in the normal sequence
> of events, so if you change a value in the control and then click a
> button without leaving the control, the button click happens first,
> before the events of the control you changed.
> 
> Charlotte Foust
> 
> 
> -----Original Message-----
> From: Francisco Tapia [mailto:fhtapia at gmail.com]
> Sent: Thursday, September 01, 2005 11:55 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Form Before Update
> 
> 
> Thanks for the response... but the event is actually the Form's
> BeforeUpdate, I tried txtADE.text but that doesnt work either. This
> whole process occurs from a command button that I use to mark a hidden
> textbox w/ a 3, so when it receives the new value, I get the
> before_update (on the form) firing.
> 
> >
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 



-- 
-Francisco
http://pcthis.blogspot.com |PC news with out the jargon!
http://sqlthis.blogspot.com | Tsql and More...



More information about the AccessD mailing list