database error during admin profile edit

I have a field called "industry" but for some reason I lost that data when I did my migration.  Now I am updating it manually by editing the member's profile in admin.  Whenever I do, however, it generates the error message below, though it still changes the record.   It is mostly just an annoyance, but is there a way to fix this.  I have to update several hundred records.

Rob

SELECT `ID` FROM `Profiles` WHERE `Status` = 'Active' AND `ID` != 10 AND `` = '12,35'

Mysql error: Unknown column '' in 'where clause'

Found error in the file '/var/www/vhosts/CALTRADE.com/httpdocs/community/inc/match.inc.php' at line 57.
Called 'getAllWithKey' function with erroneous argument #0.

Something is wrong with one of my fields - "Industry" and I can't figure out what.  As I said above, it generates errors on a profile edit, but I put this field on the "quick search" block, and it is also generate errors there.

-----------

SELECT `ID` FROM `Profiles` WHERE `Status` = 'Active' AND `ID` != 10 AND `` = '12,35'

Mysql error: Unknown column '' in 'where clause'

-----------

As you can see,  where the search field name "Industry" should be, there is just a blank.  Can anyone think of why this might be happening?

Rob

With Zarcon's help we found this was caused by the matching system (thanks Chris!).  When I turned off match making in the admin settings, the problem goes away.  I want match making, however, not for dating but to match people by industry and a few other parameters.  When I turn match making back on, and try to match my "industry" field, I get a similar error.  Note the empty quotes where the field "industry" should be.  I'm pretty sure this is a bug - it worked in D6.  Is anyone having similar issues?

SELECT `ID` FROM `Profiles` WHERE `Status` = 'Active' AND `ID` != 1 AND `` = '0,Business,ICT,Internet'

Mysql error: Unknown column '' in 'where clause'

Found error in the file '/var/www/vhosts/CALTRADE.com/httpdocs/community/inc/match.inc.php' at line 57.
Called 'getAllWithKey' function with erroneous argument #0.

Wait - posted too quick.  Forgot about the #$#(&#$  cache.  I think it may be working after all.

OK, I am back to thinking this is a bug.  It seems that sometimes, I can get a profile to enter without errors if I am editing it a second time, but on the first time it will always generate errors if matching is enabled, even if the cache has been cleared.   When I disable matching, it will work. Boonex please take note - I think there is a problem in your matching system for fields other than age, sex, etc.   If anyone else is having problems with this please let me know.