When I run the LNC Rename Current Control add-in in an existing database on a control that has VBA code behind it, the add-in changes the name of the control but does not change any of the references to the control in the VBA code.

For example,
If I had a command button named CloseForm which I created using the Control Wizard, VBA code would be automatically generated for the Click event of the command button called CloseForm_Click. If I run the LNC Rename Current Control add-in, the add-in will change the name of the control from CloseForm to cmdCloseForm, but the references to that control in the VBA code have not been changed. In particular, the CloseForm_Click is still named CloseForm_Click instead of renaming the procedure to cmdCloseForm_Click. As a result the command button click event will not work.

Is it possible that the LNC Rename Current Control add-in changes the name of the control but does not change the references in the VBA code? This just doen't seem right to me. If you change the name of the control, you should change the name every place that that control is referenced in the VBA code, especially in their event procedures.

Can anyone shed any light on what I am doing wrong? Do the changes in the VBA code have to be done separately using Find and Replace?

Thanks,
Terry Waltz

Terry Waltz

__________________
Terry Waltz

Your last sentence is correct. LNC rename does correct references to renamed database objects (tables, forms, etc.) but not to renamed controls. This can be done directly with FAR. However, I will consider this as a possible future enhancement to the add-in.

Helen Feddema
Kerhonkson, NY
[email protected]
http://www.helenfeddema.com
Read Woody's Access Watch
http://www.woodyswatch.com/waw/

Thanks for your confirmation.

Should I post this as an Errata? (I haven't had any confidence in the Errata procedure since I get no feedback and no Errata have been posted on the website) Or will you take it from here?

Terry Waltz

This is more of an enhancement request than errata. I might upgrade the add-in to include this feature, unless it looks like Access 2006 will (at long last!) include automatic application of a naming convention.

Helen Feddema
Kerhonkson, NY
[email protected]
http://www.helenfeddema.com
Read Woody's Access Watch
http://www.woodyswatch.com/waw/

I appreciate your response. Currently this is an errata issue ...

On p.295 you state "To make this task less burdensome, I created the LNC Rename add-in, an Access add-in that automates the process of renaming ... form and report controls, and also corrects references to them in code."

This statement in the book (and perhaps there are others that reference this same capability of the LNC Rename add-in) is not correct and should be posted as an errata.

I have found/reported (thru the Wrox errata form on the Wrox website) several errors in this book and in "Access 2003 VBA Programmer's Reference", but I never get any feedback from my errata submittal and nothing ever gets posted as an errata.

For many readers, like myself, reading these books are how we learn. We rely on books (and errata).


Terry Waltz