Dynamically generate query tables

ImkeF - That seems to effectively be a way to grab data from many sources and merging it all into a single table where the first column defines a 'page', and you could filter by page to look at each of the individual 'tables'. Did I get that right? It's quite different from my problem unfortunately.

Greg_Deckler - Not sure if I fully understood your paraphrase, but the use of 'automagically' leads me to think you got what I meant, and this isn't really feasible :)

To re-iterate (and add a bit of background):
We are storing custom user triggered event data in an Azure Blob - each event type will have different parameters for us to measure.

I have a table with 2 columns, [name] holds the unique event names, and [name table] is a table column whose rows point to event data for a particular event type. All tables have different data in them, eg.:

All Tables:
Event Name   | Event Data
-------------------------
Add Geometry | Table
File Saved   | Table
Registration | Table

 Add Geometry-Table:
 id  |  Outline  |  Filled
----------------------------
0    | Dashed    | False 
2    | Solid     | True

File Saved-Table:
 id  |  Date  |  Format  |  Size
-------------------------------------
3    | 01/01  |  txt     |  15
15   | 02/05  |  ppt     |  100


Registration-Table:
 id  |  Source 
---------------
10   |  website 
45   |  e-mail 

(note- the immediate tables linked are actually different, that's why I run a query function on them to get the final form, but let's ignore that step).

ImkeF - as you can possibly see, having all this data merged into a single table would make it extremely sparse and filled with nulls

What I'd want to do, is from this 'All Tables' table, generate separate new tables in my model. Right now I need to manually create a new query every time, and set the correct entry in 'All tables' as the source (or actually right click on the table link and 'Add as new query'). Ideally I would be able to have those query tables generated automatically, rather than manually, so that if we add new events we don't have to go through and create new tables every time.

I believe you can modify the model by refreshing the data in the desktop app- eg. if a table has columns generated by pivoting another column, depending on what data comes in on that column will define which new columns are created. Whether we can generate new tables in the model in a similar automatic fashion is what I'm trying to figure out.