Solved

[microwin88x]

Solved

[ajsjoshua]

Hi,

creating link table is the best way in my point of view.

Regards,

Joshua.

[marcus_sommer]

There are more common fields between the tables then different ones so that I would very probably concatenate these tables. That's easy to implement and runs often faster then link-table approaches.

- Marcus

[Anonymous]

Link table is the best Approach or You can use concatenate or use left outer join to make it as single table .

[Colin-Albert · Accepted solution]

Concatenate would be my recommendation.

You may also want to create a RECORD_TYPE field using the first character of ID_MAIN, or by adding a fixed value in the load script say 1 for Tasks, 2 for orders, 3 for Incidents so you can easily select Tasks, Orders or Incidents in your filters or set expressions.

[Anonymous]

I would go with concatenating the three tables as I'm sure you would see a better performance.

[microwin88x]

Thanks Colin.

The thing is if I need to check which orders/incidents have associated tasks, how would I do that if I use a single table? Because as I have it right now with the 3 tables by separate, from table TASKS I can know what ORDERS/INCIDENTS are associated to that task.

[Colin-Albert]

Load the Items and Tasks using

     ID_MAIN as ID_PARENT

Then you can filter on the Parent ID and the you will see all tasks and linked orders and items.

The link between the records should be on ID_PARENT not ID_MAIN.

[microwin88x]

Thank you!!!