1 of 1 people found this helpful
You can concatenate these tables using a custom sql query adding a label so you know which table it came from. Your query will be a bit different from mine, but when first edit your connection and select custom sql you'll get a good clue where you should put periods, square brackets, etc.
"Table#1" as TableLabel
"Table#2" as TableLabel
This will result in just one table, with the originals labeled, so the comparisons should be relatively easy.
You are right, I did not think of unioning the tables together. But that should do the trick. Thanks a lot!
And thanks to you too for your quick response! I should have stumbled upon one of those myself, but thanks for being my search engine
I have a buck load of fields to audit and even more controls I could come up with. So I will have to read that thoroughly to find which needs the least custom SQL to write and maintain. From skimming your linked posts, I would probably have to steal from both of the first two posts, since I want both aggregated statistics and a list of differences.