Build second version of database - Best way to do it

Hello everyone,

If this topic is not in the right place, please move it to the right place.

I've built > 10 .xlsm files, for several departments, to manage what we call SAP User Authorization Concept.
It's a 3 dimension matrix around:

Users (add/remove/edit)
Functional Roles (add/remove/edit)
Roles/Functions (to perfom a specific Functional Role, x number of roles are needed)

Function Roles is the central link between Users and Roles. A user can have one or more Functions associated, and for each Functional Role, x roles are needed.

1.png

I've also built a interface for the Dept. Database Manager to "manage" it. This interface is all VBA.
2.png
3.png

For a initial version, it was already a lot of hard work, but now, i want to have a second version to fix some of the issues i have with V1.

1. Each dept. has is own file, so whenever i need to make a change in the code, i have to go to each file and do it. So this is something to avoid.
2. I would like to have two login types. Mine that views all Depts. data, and then Database Manager/Keyuser that only views Dept data.
3. Also i would like to had reports and comparison functions.

So my question to you guys is what is the best way to this?
I've tried initially a Access Database with visual studio C# interface. But it was taking me to long, so i dropped it. Then i tried an Access - Excel combo, and same thing. I had to deliver something in a short time frame, so i did everything in Excel/VBA.

A fellow Excel expert, talked me about Power Pivot, Power Map and Power Query. I'm a complete 0 in this, so i don't know really if it can help me or not.

What is your advice on the best and simplest way to do this? I would need to have always as a end result, a matrix similar to the one i've shown you in the first screenshot.

I have experience with VBA, Access and C#, so it would have to be somewhere here. If by chance you have a database similar to what i need, please share it if you can.

Thank you.

Anyone's opinion?

Thank you

What about pure access, since you;re building a relational model it's the logical choice.

Why does it need to be Access/C#, Access/Excel etc? The reason you use access rather that SQL server for example is that it deals with the GUI and provides a RAD environment - I rather suspect (from your limited description) that you could do this purely in Access with zero coding.

Users don't need access installed to run the front end either, the free access runtime will suffice