It's a good idea to establish control names before you start coding. When you change the name of a form or report control that has code behind it, the procedure no longer runs. To solve

the problem, you need to rename the procedure to match the new control. For instance, when you first create a text box, Access might assign the name Text1 to the control. If you attach code

to the control's AfterUpdate event, the procedure begins with the statement

Private Sub Text1_AfterUpdate()

If you later give the textbox a more meaningful name like txtDateAdded, you need to change the name of the procedure to Private Sub txtDateAdded_AfterUpdate() When you change the name of the control, the procedure attached to it becomes orphaned. To locate orphaned procedures, select General from the VBE's Object dropdown list. Then, review the contents of the Procedure dropdown list. In addition to procedures 

and functions you've specifically created, you'll find any orphaned procedures.

Access Index

Main Index