Possible avenue of discovery and resolution(1): If you are using Power BI Desktop 64-bit and Access Database Engine 2010 OLEDB provider 32-bit, or vice versa, there might be a mismatch that causes an error when importing data. To fix this mismatch, the user can either install the matching bit version of the Access Database Engine, or use the ODBC connector instead of the OLEDB connector to connect to the Access database.
Possible avenue of discovery and resolution(2): If you are using Power BI Dataflows to import data from an Access database that contains lookup fields, there might be an issue with the connection set that prevents the lookup values from showing up. To resolve this issue, the user can go to the Power Platform admin center and edit the connection set related to the Dataflow.
Possible anenue of discovery and resolution(3): If you are importing directly including your lookup fields and some of the data looks good in the Power Query Editor but not in Data Model or Report view then you might have a refresh model.
I might do the heavy work in the data model in power BI instead of Access instead. But you know your tools and data better and your solution might be fine.
