[AccessD] Accessing AfterUpdate Event from another procedure

In that case, what you should do is have a public method that is called
by both the afterupdate event of the form and wherever else it is
needed.  It's kind of sloppy to expose the internal events of a form
because some of the necessary underpinnings might not have occurred when
you call that event.

Charlotte Foust 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Borge Hansen
Sent: Tuesday, August 29, 2006 7:57 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Accessing AfterUpdate Event from another
procedure

David,
Not possible here as I want to execute whatever the afterupdate event
does from another place in the application....
Problem solved though, see previous post....
Borge

----- Original Message -----
From: "David & Joanne Gould" <dajomigo at tpg.com.au>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Sent: Wednesday, August 30, 2006 12:40 PM
Subject: Re: [AccessD] Accessing AfterUpdate Event from another
procedure


> Borge
> 
> I would add the code into the AfterUpdate event module attached to the

> combo box itself, unless I have misunderstood your question.
> 
> David
> 
> At 12:16 PM 30/08/2006, you wrote:
> >Hmmmm...
> >I always seem to get stuck when attempting to access and run code in
an 
> >afterupdate event when trying to call and execute the event
> >from another procedure in another module than the Form module the 
> >afterupdate event code resides in....
> >
> >So what are the clear cuts on this.... please
> >

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com