index/match: construct 2 new 'tables' from 1 dynamic 'table'

folks,

hopefully this description makes sense:

1. i have a 'table' in excel2013 built from 'get external data'; hence the rows might/will be dynamic; the refresh cycle is 1x per week

now,
2. the primary keys of the rows in 'get external data' need to be used to pull complimentary data from 2 other 'get external data' extracts
3. hence, the table in item[1] is the dynamic driver to 2 other searches; the 2 'next' searches only have to return data for the primary keys determined in item[1]
- one of these tables does a 'get external data' from a source that refreshes 1x per day
- one of these tables does a 'get external data' from a source that refreshes 1x per week

so there are a few ways to solve this:
4. add ALL the needed columns into the item[1] 'table', and figure out how to manage the 3 refresh cycles perhaps via some 'form' control
5. build the 2 'next' search tables on the fly via some kind of event driven macros, let these tables refresh separately, and build a consolidated 'result' table out of the 3 tables [same set of primary keys, after the 3 refresh cycles to 3 different sources, refresh and complete]

hence
task1: figure out how to manage 3 independent refresh cycles from a single table
or
task2: figure out how to build 2 table structures [at least for the primary key column; the other columns are static and specific to the other data sources] on the fly from the item[1] table

i'm not quite sure exactly which task is easier, and really, how to begin either. i can 'think' the problem, but i haven't tried to 'construct' either task.

any feedback would be appreciated?
thanks,
ron

Seems easier to just build a new table that is linked to your dynamic table [1] and then performs =VLOOKUP calculations to populate whatever data you want from the other two tables.

hoya,

I thought of that, but I didn't think I could make it work.
the 'dynamic' table returns a different number of rows each time [meaning: the rows are unique, the primary keys differ frequently, so I might get 15rows, then 27rows, then 5rows].
based on the number of rows [or better, the different range of primary keys], then the primary key list is given to the 2 other tables for their extracts to be performed.

since the keys are the drivers, I wasn't too confident on how to code vlookup in that situation.
I will think on this some, and also re-look at the 2 subsidiary tables. maybe I can do a download of their entire contents, and that would guarantee that vlookup would be against a static table.

thanks for the feedback.
ron