My suggestion: Why not having *one* select statement to txxxInput Component on *each* main data row, which requires a join. let Oracle or other db's do the caching or whatever appropriate. Why building again hash-tables and files ?
Would that be a difficult code-change to a tJoin or txxxInput (lookup) component ?
Could you please explain what is meant with: "New high performance lookup mode supporting multi-gigabyte tables and files " as stated in recent newsletter apraising 2.4?
Is it the "swap to file" option in tOracleInput ? or anything else really high performing ?