In the general case the answer is no; it's possible for any kind of custom action (or Windows Installer itself) to refer to properties for which you won't see other references in the database, and it's possible for InstallScript actions to reference strings. However if you know you're not doing things like that, searching the tables is probably good enough. In the string editor view it should be possible to search for uses of strings, but it may or may not report bulk results in a format that's useful for you. I don't think we have anything similar for properties (largely because of how many properties are read in other ways).
Michael Urman - Staff Software Engineer - Flexera Software: InstallShield Team