MS Access / SQL Reporting Specialist for Microsoft Fabric + Power BI Environment

We are a beverage alcohol sales organization in Oregon building a more stable reporting environment using Microsoft Fabric, MS Access, Power BI, SQL, and Excel/CSV operational outputs. This is not a generic Power BI dashboard job, and it is not a standalone MS Access database job. We need someone who can help build and stabilize the reporting layer between Microsoft Fabric, MS Access, and Power BI. Current environment: We already have a Microsoft Fabric warehouse with core dimensions and fact tables. Fabric should remain the data foundation and source of truth. MS Access will be used as an operational reporting workbench for detail reports, exception reports, QA/reconciliation, legacy report stabilization, linked-table workflows, ad hoc analysis, and exportable files. Power BI will be used for dashboards, trend reporting, client-facing visuals, supplier reporting, and recurring executive summaries once reporting logic is stable. We already have a Fabric engineer working on the core warehouse/data environment. This role is not intended to replace that person. The goal is to help turn approved Fabric data/views into stable, usable reporting outputs while making sure Access, Fabric, Excel, and Power BI do not produce conflicting answers. Primary work: Review and stabilize existing MS Access reporting assets, including queries, reports, linked tables, and ODBC workflows. Help set up a clean Access reporting environment that connects to approved Fabric views or SQL/reporting views. Help design and validate Access-ready views for reporting, rather than importing large raw fact tables into Access. Create or support small controlled reference/mapping tables where business definitions are missing. Write SQL queries for validation, reconciliation, reporting extracts, and QA checks. Create practical Excel/CSV outputs for sales reps, GIS mapping, RoadWarrior routing, supplier reporting, and client meeting preparation. Support Power BI reporting from the same approved Fabric views or reporting tables used by Access. Document report logic, joins, filters, calculations, assumptions, and business rules clearly. Help decide what belongs in Fabric, what should be handled in Access, and what should eventually move to Power BI. Business context: We work with OLCC liquor sales, inventory, store, supplier, item, and account data. The reporting environment needs to handle store numbers, item numbers, supplier numbers, premise/account identifiers, item descriptions, territories, areas, reps, account lists, supplier/client groupings, and 9-liter equivalent reporting. Some OLCC source reports use different item description formats for the same item. Item number should generally be treated as the primary join key, with source-specific descriptions preserved where needed. Item numbers need to be linked to bottle size, liters per bottle, and 9-liter equivalents. Store type matters. Normal 1xxx liquor stores should be separated from 3xxx and 9xxx locations. For now, 3xxx and 9xxx locations may be treated as separate unknown store types unless better definitions are confirmed. The first phase is not to build every report. The first phase is to help create a stable reporting structure so Access, Fabric, Excel exports, and Power BI can work together cleanly. Ideal candidate: Strong hands-on Microsoft Access experience, including linked tables, ODBC, queries, reports, troubleshooting, and legacy database cleanup. Strong SQL skills. Comfortable working with SQL Server, Azure SQL, Microsoft Fabric, or similar warehouse/reporting views. Comfortable with Power BI and modern reporting workflows. Understands fact/dimension structures and practical business reporting. Able to document work clearly. Comfortable working with an existing Fabric/data engineer. Understands that reporting must be useful for non-technical sales, management, and supplier users. Individual freelancer preferred. I am not looking for a large agency or a team that will hand the work off to multiple people. Possible first phase: Review the current Access reporting situation and available Fabric reporting structure. Recommend how Access should connect to Fabric or approved reporting views. Identify which Access-ready views, reference tables, or mapping tables should be created first. Build or stabilize one high-value Access reporting output as a proof of concept. Validate the output against Fabric/source data. Document the joins, filters, calculations, assumptions, and business rules. Please respond with answers to the following questions: What is your specific hands-on MS Access experience? Please mention linked tables, ODBC, queries, reports, forms, macros, or VBA if applicable. Have you used Access alongside SQL Server, Azure SQL, Microsoft Fabric, Power BI, or another warehouse/reporting environment? Please describe one example. Have you helped decide what should stay in Access versus what should move to SQL/Fabric/Power BI? How did you approach that decision? How would you approach the first 10–15 hours of this project? How would you prevent conflicting definitions between Fabric, Access, Excel exports, and Power BI? Are you strongest in MS Access, SQL, Power BI, Fabric/data engineering, or reporting architecture? What is your hourly rate and weekly availability? Are you personally doing the work, or would this be assigned to another person on your team? Please do not send a generic Power BI dashboard proposal. I am specifically looking for someone who can help with a hybrid MS Access / SQL / Microsoft Fabric / Power BI reporting environment.