Orphaned Code

  • Thread starter Thread starter Gordzilla
  • Start date Start date
G

Gordzilla

Is there anyway of finding orphaned code behind forms and reports.

ie. Control was named txtDesc with various code attached to events.
Control was changed to a combo box and renamed to cboDesc.
All of the original code still refers to txtDesc.
I would like to be able to find any code that is no longered associated with
a control and either correct it or delete it.
 
Gordzilla said:
Is there anyway of finding orphaned code behind forms and reports.

ie. Control was named txtDesc with various code attached to events.
Control was changed to a combo box and renamed to cboDesc.
All of the original code still refers to txtDesc.
I would like to be able to find any code that is no longered associated
with
a control and either correct it or delete it.

Open the form's class module, put the cursor in the declarations section (ie
before any procedures), and drop down the right hand combo. They'll all be
visible there.
 
Perfect exactly what I wanted.

Stuart McCall said:
Open the form's class module, put the cursor in the declarations section (ie
before any procedures), and drop down the right hand combo. They'll all be
visible there.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Orphaned Code Segments 3
Orphan Code 2
Code actually being used? 4
Displaying images 1
Read text of form/report module code via VBA 6
Record update 2
Access OpenArgs in Access 2010 failing 0
How to Find Orphan Images? 3

Back
Top