Introduce a special case into Code References, to analyze what portion of the line is being replaced, only when it searching property values?

No, I would hate to do that.


>What if it were limited to only change the VALUE of a property that matched the search expression, and not the property name?
>
>
>
>
>>Risky for a few reasons:
>>
>>(1) Definitions for custom properties / methods are stored in two places in the SCX / VCX. Modifying only one of the places could cause the definition to be lost altogether.
>>
>>(2) If you made a typing error when mucking with either of these two places, creating an invalid name, you could conceivably damage the file sufficiently that you could not open it with the Forms / Class Designer.
>>
>>In either case, of course, you could use HackCX to try to correct things. Then again, if you made a fairly large number of such changes, resorting to HackCX could be quite painful ...
>>
>>You can always be careful to avoid such problems .... but, somehow, no matter how careful I am, it always seems like I still get things wrong on occasion. On those occasions, making a form unusable (or partially trashed) seems like a heavy penalty.
>>
>>
>>
>>>>>>>I an renaming many field names in some of my table, and now I have to update the various pieces of my app to work with the new schemas. Some places that will need to be fixed are the .ControlSource property on many objects, code in methods of forms and classes, and fields in reports.
>>>>>
>>>>>Have you tried gofish, available in downloads here? It has options for search and replace in scx, frx, dbc, vcx etc etc...
>>>>
>>>>Hi,
>>>>
>>>>Indeed GoFish is also an excellent option to replace, although it seems the Codereference is a bit faster.
>>>>
>>>>Regards,
>>>>
>>>>Koen
>>>
>>>One major difference is that GoFish will perform a search-and-replace on property names and property values. Code References will not do this. Jim Nelson thinks it's too risky to attempt.