Forum Discussion
Why the Dataverse connector?
Can anyone explain to me why Microsoft added a Dataverse connector to Access when you can't share an Access DB using Dataverse tables? I would love to know the logic on that piece.
> can't share
You mean such apps are single-user?
Have you seen this: https://powerusers.microsoft.com/t5/Building-Power-Apps/How-to-control-app-and-Dataverse-access/td-p/2198251
You mean such apps are single-user?
Have you seen this: https://powerusers.microsoft.com/t5/Building-Power-Apps/How-to-control-app-and-Dataverse-access/td-p/2198251
- Hi Tom,, I am trying to share an Access front .accde file (app) using Dataverse tables as the backend. Not a Power App. Unfortunately, users cannot access the DV tables because the .accde file renders them as read only. The huge error with the Access DV connector is that it won't map to a DV solution, which is probably why I can't share the DV tables as read/write tables. In any case, as I just stated here, it looks like I will have to go old school and build a local SQl server machine. Dataverse is simple not a viable solution for Access, which is why I asked the question, "Why the Dataverse Connecter?" It's an incomplete solution apparently implemented by people who probably never used or developed an Access DB.
"The huge error with the Access DV connector is that it won't map to a DV solution" What does that mean in this context? "won't map to a Dataverse solution"? If you mean what I think you mean, it's not accurate. I actually have an Access accdb linked to Dataverse tables in a solution.
But perhaps you mean something entirely different?
I take that back. I actually have two accdbs linked to Dataverse tables in two different Solutions.
