Does "WHERE Like", when used on a field name, return an exact match like an equijoin, or does it return similar data as if a wildcard is used?
Example: I have to compare the contents of two fields, each in its own two table, and present consolidated results. Let's call them A.COMPANY and B.COMPANY. Both fields contain overlapping data that represent the same real-world companies.
An equijoin pulls up a number of exact matches. But I want to see if there are companies that match but have slightly different spellings, an additional comma or period, etc.: e.g., "USA Company Inc" vs. "USA Company, Inc." I use "WHERE Like [A].[COMPANY]" I get back the same results as the equijoin. Trying wildcards doesn't work with a field name. At least, I can't figure out how to use them.
Is the "WHERE Like" acting like an equijoin and ignoring near matches? Or is the data in both fields and tables exactly match? (Not impossible, but unlikely.)
If "WHERE Like" acts like an equijoin, how can I find near matches on two fields?
Thanks!
Example: I have to compare the contents of two fields, each in its own two table, and present consolidated results. Let's call them A.COMPANY and B.COMPANY. Both fields contain overlapping data that represent the same real-world companies.
An equijoin pulls up a number of exact matches. But I want to see if there are companies that match but have slightly different spellings, an additional comma or period, etc.: e.g., "USA Company Inc" vs. "USA Company, Inc." I use "WHERE Like [A].[COMPANY]" I get back the same results as the equijoin. Trying wildcards doesn't work with a field name. At least, I can't figure out how to use them.
Is the "WHERE Like" acting like an equijoin and ignoring near matches? Or is the data in both fields and tables exactly match? (Not impossible, but unlikely.)
If "WHERE Like" acts like an equijoin, how can I find near matches on two fields?
Thanks!