andrewgb wrote:so how do you manage two foreign keys in a table to the same primary key?
One common option is to duplicate a table, which isn't practical for your case. But to cover what that would look like just so you know, the table with SClaim_ID and EClaim_ID would stay the same, but your other tables would all get SClaim and EClaim versions, keyed by SClaim_ID and Eclaim_ID respectively, and with all of the other field names renamed to match the table they're on, like for instance SClaim_Date or some such instead of Date. That's a huge amount of extra data and extra complexity, and almost certainly not what we want here.
Another option, perhaps a bit less common, is to create a new table just for the references from the first table. So if your current data looks like this:
UniqueKey, SClaim_ID, EClaim_ID, OtherField1, OtherField2
1, Claim1, Claim2, A, B
You would convert that data to two tables, one of which has two rows for the key:
UniqueKey, OtherField1, OtherField2
1, A, B
UniqueKey, ClaimType, Claim_ID
1, SClaim, Claim1
1, EClaim, Claim2
Converting columns into rows is fairly simple in QlikView. And there's very little extra data here, and the main extra data (ClaimType) will be heavily compressed. So this is a much more practical option than the first, but since I don't know what you want to DO with the data, I can't tell you if it's an appropriate solution. All I can say is that it resolves the linkage problems, because now both claim IDs will map to the other claim tables.
