[AccessD] Losing control event connections

Griffiths, Richard R.Griffiths at bury.gov.uk
Thu Feb 27 07:12:00 CST 2003


Doug

I believe you can also do this:

1 enter code module
2 cut all code
3 paste back all code

Access then reassigns those 'missing' event procs

Richard
Manchester, UK

> -----Original Message-----
> From:	Gustav Brock [SMTP:gustav at cactus.dk]
> Sent:	27 February 2003 12:44
> To:	Doug Murphy
> Subject:	Re: [AccessD] Losing control event connections
> 
> Hi Doug
> 
> It happens if you rename a control, or if you paste/write code for a
> control directly in the code window without passing and selecting
> Event Procedure for that control. I haven't seen this behaviour else.
> 
> Sometimes Access discovers this, sometimes not. It is easy to repair:
> just select Event Procedure for the control, open the code and close.
> 
> Also, once I had an (Access 2.0?) add-in which fixed it automatically
> but I've lost track of it.
> 
> /gustav
> 
> 
> > I seem to recollect past discussions of something causing form controls
> > to lose the connection to code subroutines for their events; that is
> > there is a subroutine for a control event but it does not show in the
> > controls event properties and does not fire when the even occurs.  I
> > just ran into a form today that was working and now does not work.  When
> > I looked the event subroutines are there but the properties are not set.
> > There are three controls with this problem.  None of them have been
> > renamed.  This is an Access 97 database.
> 
> > Has anyone else experienced this behavior?  Anyone know what causes it?
> 
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
--------------------------------------------------------------------------------------------------------------------
This e-mail, together with any files transmitted with it, is
confidential and intended solely for the use of the individual to
whom it is addressed. If you are not the intended recipient, or
the person responsible for delivering to the intended recipient,
be advised that you have received this e-mail in error and that any
use, dissemination, forwarding, printing or copying of this e-mail
is strictly prohibited without liability on our part.

If you have received this e-mail in error please notify the sender.



More information about the AccessD mailing list