Thanks for the response. I dunno why I thought that would create synthetic keys. What's happening in my load script is that associations are being created when those three are loaded (as you mentioned, no synth keys). Following that, I have another table that contains items from all three tables:
(biff, embedded labels, table is Sheet1$);
This then creates the synthetic keys. So I'm wondering if there is way to avoid the synth key in this case without joining the first three tables first and creating a mapping key (sorry for explaining so poorly initially)
can you attach a screenshot of your Data Model (ctrl+T).
for Synth keys which you think are not really Important(key fields) you can just rename them,
another way is to Qualify all fields (*) or qualify only the fields you want, in this case, synth field.
There are plenty of ways to avoid Synth keys if you dig a bit more i the forums, might be useful to your current requirement.
You need to choose by which key field (of BUSINESS_DESCRIPTION, MANUFACTURER_NAME, ADDRESS) you want to link the transactions to the main table.
Are the other possible key fields in this spreadsheet redundant (ie the same as what has already been loaded in the main table), or do they differ (ie BUSINESS_DESCRIPTION is associated with a different MANUFACTURER_NAME and/or ADDRESS than in the main table)?
based on the info you provided …
my guess is it makes sense to join the first two tables and build a combined key in the new table from BUSINESS_DESCRIPTION and MANUFACTURER_NAME (BUSINESS_DESCRIPTION &’_’ & MANUFACTURER_NAME as %BDMAN) and rename the fields to something else in both table. Then load the Transaction Table also with the new Key like shown above and rename the two fields here as well.
Then load the Area table like you do right now ….
If you could send me a sample qvw with some fake data I could show you better what I mean …