Forum Discussion
Why the Dataverse connector?
"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?
- George_HepworthSep 08, 2023Silver Contributor
I take that back. I actually have two accdbs linked to Dataverse tables in two different Solutions.
- RexterSep 08, 2023Brass Contributor
I have not found and way to export Access tables to a Solution. I tried several times and the tables only export to my environment. I am thinking you have a different subscription than I do. My organization has a 365 Business Premium sub, but apparently, we need an Enterprise sub for full SharePoint & Dataverse capabilities. No budget for that. I tried using Sharepoint lists as a temporary measure, but I am having the same issues. Appearently, Access Combo box won't write to a SP List of Davaverse. So, I ask again, what is both connectors?
I was told that SP Lists and DV can't be used as data sources for Access. Now I clearly see that they were correct. Hoping I get budget approval for an SQL server soon. In any case, dataverse is a far too a complicated platform. It requires heavy IT support. I am an Access developer, not an IT engineer - not suitable for non-IT developers.
- George_HepworthSep 08, 2023Silver Contributor"I was told that SP Lists and DV can't be used as data sources for Access"
That is flat out inaccurate.
We've been using SharePoint lists with Access since at least 2003. Access Web Databases, released in Access 2007, used ONLY SharePoint lists. In other words, the exact opposite is true. SharePoint lists work just fine. And so do Dataverse tables.
It may well be that Dataverse is too demanding for your needs, though. That's different from "can't be used".