22.214.171.124 REFUSES to compare based on my CUSTOM KEY settings
This happens to be an important audit table, of a mere 7 columns, the int real PK plus the 2 Audit columns, datetime and an IDENTITY int, are the three custom key columns and the other 4 simply match on name - witnessed by opening the "columns in comparison" for the table just to make sure I'm not losing it entirely. I "Save". I "Compare Now". I get frustrated because the tool says I don't have mapping - WHAT?
Every other table (over 30 of them) in the "audit" database compares using the same principle, and they ALL, without exception, map just fine using the real PK plus the 2 audit columns, and they compare just fine, too.
Please fix this or tell me where a hidden-away setting or remnant of another .sdc file could be - I Edited an existing .sdc and "Save As..." to create this project. As there are NO PK's actually defined to any of the over 30 tables, I have to map them all by hand, so please, if at all possible, don't advise me to "scrap the project and start over" :evil:
BTW: I inherited this steaming pile four weeks ago - would NOT have designed the DB this way in my worst dreams, so please don't anyone comment on "why is it defined this way?"