this sounds like you just want to do a join.
Do you expect your end result to be something like this:
employee field1 field2
a 1 4
b 2 5
LOAD * FROM Table 1
LOAD * FROM Table 2
Or do you have shared value fields, in which case you want to use a CONCATENATE.
Use the JOIN keyword, that you can precede with LEFT or RIGHT.
LEFT meaning that only the employees from table A will be merged. RIGHT means that only employees from table B will be in the future table.
Because you have several employee rows in table B, you will have to to a sum(...) GROUP BY employee to get an effective merge. sum() or any aggregation SQL function for all the fields you want t import from table B
And INNER join will leave no nulls on both sides.
In QlikView the simple join is FULL OUTTER by default. That matches QlikView philosofy and associative model. There is always a way to take away null values.
The question is, How many fields in common have your tables. If there is only one common field Employee_id, do the join; If they are many common fields, do concat.
If records are from the same nature, concat.
I guess you all have it right somehow, swuehl was merely the first.
It is indeed so easy I didn't see it - of course, concatenating and then sorting will do the trick.
That will help keep the whole thing slim - I will have to build a subroutine and call that once for every employee, about 1k times, so if I don't have to do so much concatenating in the subroutine, that will keep the final execution_time low.
Thanks a lot!