Monster Syn Table.

[#1]

Hey guys i once more created a monster in qlikview.

I Hope you guys can see what is going on but i have a projecttime table which holds hours worked.

And the sales invoice tables to count made transactions made by employees. I need both those employee's te be the same to make some calculations.

My report works perfect i do have a huge syntable which i want to remove. Anyone has any ideas?

Thank you Luuk

[#2]

Hi

Please find the attachment.

Hope it helps you.

[#3]

Doc for tht application.

[#4]

Thanks for you quick responce i think i understand how it works but i dont know which tables i should use in my

File. Any chanse anyone could make 1 small example?

[#5]

Can you share you application File ???????

It will be better option for us then !! 🙂

try removing the common fields name by different tech available.

[jonathandienst]

Luuk

IMHO synthetic keys are not intrinsically evil. They are ugly on the table view, but not necessarily evil. If your data model is correct, and your reports/charts perform fine, then you don't need to fix it. "Fixing" the syn key could break your report.

Often, though not always, synthetic keys are evidence of a poor data design. If your model is good, then the syn key is fine.

Jonathan

[#7]

For that please load ur application.

wil try it

[#8]

Hi,

Synthetic keys are not as evil as one might think but they will make your table viewer look confusing and they will increase your load times.

If you are certain that you require them, then add the following line to each of the tables generating synth keys:

autonumber(PK_R_EMPLOYEE & '_' & PK_R_SALESINVOICE) as PK_R_KEY,

and rename the PK_R_EMPLOYEE and PK_R_SALESINVOICE fields to something different in each table so that Qlikview doesn't try to link them.

The reason why autonumber is used is because Qlikview is much more efficient at linking numbers than text.

Use the same logic everytime you get synthetic keys and you will be fine.

Danny