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 shareYou 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, I'm not sure what you mean by "can't share an Access DB using Dataverse tables". You should be able to share it with other users. The users must be members of the tenant and environment where the Dataverse tables live and have the right permissions set. I see no difference in these requirements for Access compared to other frontends and users for Dataverse like Power Apps etc. ServusKarl****************Access Bug TrackersAccess NewsAccess DevConAccess-Entwickler-Konferenz AEK

Karl_Donaubauer I think I found the error.. Users cannot use an encrypted Access front .accde file which renders the dataverse like a read only file. I am testing a new solution. It looks like users need the full .accdb file instead. The downside is that I have install the full file with all the local tables and dataverse tables, so dataverse clearly isn't a viable datasouce for a networked Access environment for me. I was hoping DV would actually replace the need for local SQL server machine, but doesn't seem to be the case.

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?

Why the Dataverse connector? | Microsoft Community Hub

Tom_van_Stiphout
Steel Contributor
Sep 08, 2023
> 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
- Rexter
  Brass Contributor
  Sep 08, 2023
  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.
  - George_Hepworth
    Silver Contributor
    Sep 08, 2023
    "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?
Karl_Donaubauer
MVP
Sep 08, 2023
Hi,

I'm not sure what you mean by "can't share an Access DB using Dataverse tables".

You should be able to share it with other users. The users must be members of the tenant and environment where the Dataverse tables live and have the right permissions set. I see no difference in these requirements for Access compared to other frontends and users for Dataverse like Power Apps etc.

Servus
Karl
****************
Access Bug Trackers
Access News
Access DevCon
Access-Entwickler-Konferenz AEK
- Rexter
  Brass Contributor
  Sep 08, 2023
  Karl_Donaubauer
  
  I think I found the error.. Users cannot use an encrypted Access front .accde file which renders the dataverse like a read only file. I am testing a new solution. It looks like users need the full .accdb file instead. The downside is that I have install the full file with all the local tables and dataverse tables, so dataverse clearly isn't a viable datasouce for a networked Access environment for me. I was hoping DV would actually replace the need for local SQL server machine, but doesn't seem to be the case.

Forum Discussion

Why the Dataverse connector?

Share

Resources