Yep! Kudos, cylicom !
Configuration -> Security -> Check database integrity and save - FIXED the error PERFECTLY (and painlessly).
AMAZING TEAM ACY: Perhaps institute this into the next upgrade so it does it automatically? Before I found this thread, I tried updating (to 7.2.1) to see if it would fix it - it didn't ;-)