A quick solution (I would try if I was you) would be to merge the Sales and Sets table and then join the Sales table to Target using the SupplierSet# thereafter. However I think you need to check if that has an impact anywhere else in other tables.. But this is a real quick solution which I tried sometime back and seemed it worked. Even I am new to QV but its really good and Easy to use.
I mean to say you have something like Tablename and the load statement TARGET: Load * from Target, SALES: Load * from Sales, SETS: Load * from SETS (add this script at the end: Resident SALES DROP TABLE SETS;) after the load statement for SETS you are asking to store the data from that into the Sales table and then drop the SETS table. Then you would need to rename the Customer in the Target or Sales table to avoid loops and QV thereafter links both these tables with the SUPPLIER SET# automatically.
Please try around this then you might know whats happening and learn different ways.
This is what i have:
LOAD [SET]&'-'&[SET TITLE] AS [SUPPLIER-SET],
(biff, embedded labels, table is [SUP-SET$]);
DROP TABLE sets;
CUSTNO as customer
(biff, embedded labels, table is Sheet1$);
by dropping the table sets, the targets table stays unconnected. Thanks again for the help
As new_user3 suggested, left join your supplier sets onto your Sales table. Yes, you get a synthetic key. That synthetic key tells you that the relationship between sales and targets are by supplier set and customer. That is your intended relationship. The synthetic key is therefore relating your data the way you intended it to be related. It's not a problem; it's a solution.
testJoin5.qvw 122.8 K