One problem is that a certain reference may appear in several places: within the code, as a property, in a .H file, etc.
You can search for files that contain a certain text. If the file is a class library, you can generate code with the Class Browser, to figure out the exact class. The Class Browser might also help to get a complete definition of a form, in case the reference doesn't precisely appear in code.
HTH,
Hilmar.
>We've all done it I'm sure. Re-used code from one project in another and forgotten to change the path references.
>
>In most cases its fairly simple to sort but every now and then I come across really irritating examples, where the project will complain (on entry or on compilation) that such and such is missing. And it doesn't tell you where the damn thing is being referenced so that you can fix it.
>
>Sometimes the code reference tool comes to my rescue, and sometimes it too fails to find any of the offending references.
>
>Where else can we turn at this point?
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
