By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,841 Members | 1,761 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,841 IT Pros & Developers. It's quick & easy.

VBA Event Procedures in Form Module Lost Association to the Control on Form

P: n/a
Tim
I am using ADP projects in MS Access 2002.

I have a recurring problem that happens rarely but I don't know why.

I will have code form an event procedure on a control (e.g. the
"OnDoubleClick" of a text box) that will work fine for months. Then
suddenly, the VBA code will be in the module unchanged, but it will
somehow lost its association with the control on the form! If I go to
the control's properties and look at the Event there is nothing there
even though the code for that event is in the form's module! I can
click the "..." as if I were going to write new code and it suddenly
remembers the code is there and associates it. It puts back the
"[Event Procedure]" notation in the controls for the property.

Anyone have any ideas what could be causing this? I know it has
happend to me in two different databases with text box events (one for
On Double Click, the other for After Update).
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
"Tim" <ti*******@yahoo.com> wrote in message
news:14**************************@posting.google.c om...
I am using ADP projects in MS Access 2002.

I have a recurring problem that happens rarely but I don't know why.

I will have code form an event procedure on a control (e.g. the
"OnDoubleClick" of a text box) that will work fine for months. Then
suddenly, the VBA code will be in the module unchanged, but it will
somehow lost its association with the control on the form! If I go to
the control's properties and look at the Event there is nothing there
even though the code for that event is in the form's module! I can
click the "..." as if I were going to write new code and it suddenly
remembers the code is there and associates it. It puts back the
"[Event Procedure]" notation in the controls for the property.

Anyone have any ideas what could be causing this? I know it has
happend to me in two different databases with text box events (one for
On Double Click, the other for After Update).


This will happen if you cut n' paste the control or if you change the
control's name. Other than that I would suspect that the form is
corrupted.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.