Forum Discussion
Microsoft Access database nested tables
- Anonymous9 years ago
Hi JoostttP,
Based on my observation, when loading tables from Access database to Power BI Desktop, Power BI Desktop imports the columns in these tables as well as Object Dependencies of these tables into Query Editor, and Power BI treat the dependencies as new columns of these tables.
For example, for order table in Access database, there are other 8 objects depending on it, Power BI Desktop puts the 8 objects as additional columns in order table. From my point of perspective, this behavior is proper, Power BI Desktop loads all properties of a table(data and dependencies), it doesn’t ignore dependencies and it makes us easy to select values from related tables.
Moreover, if you don’t want to retain these additional columns, you can directly remove these columns in Query Editor of Power BI Desktop or delete the object dependencies of your tables in Access database.
Thanks,
Lydia Zhang
Hi JoostttP,
Based on my observation, when loading tables from Access database to Power BI Desktop, Power BI Desktop imports the columns in these tables as well as Object Dependencies of these tables into Query Editor, and Power BI treat the dependencies as new columns of these tables.
For example, for order table in Access database, there are other 8 objects depending on it, Power BI Desktop puts the 8 objects as additional columns in order table. From my point of perspective, this behavior is proper, Power BI Desktop loads all properties of a table(data and dependencies), it doesn’t ignore dependencies and it makes us easy to select values from related tables.
Moreover, if you don’t want to retain these additional columns, you can directly remove these columns in Query Editor of Power BI Desktop or delete the object dependencies of your tables in Access database.
Thanks,
Lydia Zhang
- JoostttP9 years agoRegular Visitor
Hi Anonymous,
Thank you for your response. I figured it would be something like this. Thank you for your explanation.
What is your opinion on either merging the additional data this way or importing both tables first, and then create a merge based on a shared ID? What would be faster is perfomance you recon?
Thanks,