Just a short post this evening.
If you want to know what is next for Microsoft Access then be sure to attend the Bringing Microsoft Access into the Future: Introducing the Microsoft Access Connector for the Microsoft Power Platform session at this year’s Microsoft Ignite.
This session will highlight how Access integrates with the Power Platform
how Access databases can be migrated to Dataverse
Do notice the word migrate though! To use Dataverse, you effectively have to ditch Access as your back-end provider. This has both Pros and Cons, like with most anything. This will be your opportunity to see what is coming to the realm of Microsoft Access in the very near future.
The session is being held on Tuesday November 2nd, 2021 (it is on page 13 of the Tuesday tab of the Session catalog as of the time of writing this post). That said, I have been unable to locate an actual time for this session!????
You can also find out more about the Access Dataverse connector by reviewing Michael Aldridge’s article entitled: Enhancing the Benefits of Microsoft Access in the Cloud with the Power Platform.
What are your thoughts on the matter after viewing the video and/or reading the blog post? Please drop a comment and share your thoughts.
Again this is another circus for MS and Access development team.
Agree on the “circus” comment…but then, I have always enoyed the show! Thanks DP, I will be sure to attend.
Looks interesting, hopefully power platform gets more affordable license though
Well, I just watched it and to sum it up in one word: underwhelming.
I see no real advantage to Dataverse over SharePoint from what was featured, with the exception of table relationships and possibly referential integrity. I take into consideration that 20 min is not enough time to cover everything but I still didn’t see anything that made me excited.
Their “why Dataverse over SQL Server” bit was weak as well.
Interested in what others think…
I was disappointed with the presentation. For introducing a new feature, I don’t get 17 minutes. You’d think they’d cover more, especially trying to convince us of the benefits it supposedly has to offer.
I have yet to see the benefit over existing Azure SQL hybrid solutions!
You’ll also notice that Microsoft’s solution, right or wrong, has been to migrate away from Access. The presentation promotes more Dataverse, PowerApps, PowerBI, … So take your data out of Access, put it into Dataverse, and then use other tools. This has been possible for several years already through things like Azure SQL.
I’m just not seeing the true benefit, and the presentation hasn’t helped on that front.
Also, mentioning over and over Low code, No code and Access does such a disservice to Access. It is its code that empowers it to go above and beyond just basic tasks. It is actually insulting in my opinion, but it’s all about pushing all those buzz words and hyping other products.
I also find the title to be misleading in nature as the presentation has little to do with Access. It was more oriented on Power Platform, PowerApps, Teams than actually Access. If it was truly about Access, then why was the presentation not actually given by the Access Principal Program Manager, but rather by Nathan Helgren who is the Dataverse Senior Program Manager?
I still would like a true, proper presentation, true pros/cons. Why go this route vs SharePoint, Azure SQL, … File storage just isn’t enough of a reason for my needs. I would have expected a presentation to MVPs to entice us.
There was no mention of costing which is always a huge question!
Also, after watching some Youtube videos on Dataverse, I have other concerns as well.
What sort of concerns about Dataverse do you have?
From what little I’ve delved into that (mostly from other MVPs videos), the programmability -vs- Access and SQL Server seems…quite lacking, but that could just be me not digging in deeply enough to see it yet.
According to a video on the subject of Dataverse, once you create a field/column, you cannot rename it. So you have to jump through extra hoops- create a new column, copy the data over, delete the existing one.
I also would like more clarity on backups, exporting the data out of Dataverse if so needed…
I also have yet to see the big advantage of Dataverse over Azure SQL which can use PowerApps, Power Automate (previously Flow), …
They kept pushing the Low Code/No Code, but when it comes to databases, is that truly what we should be going for??? Look at the mess people get into using Excel, Dataverse may end up an even bigger mess.
I think we need a lot more than a 17 minute presentation! and certainly one more Access-centric and not all about PowerApps, Power Automate and Apps for Teams.
“Also, mentioning over and over Low code, No code and Access does such a disservice to Access. It is its code that empowers it to go above and beyond just basic tasks. It is actually insulting in my opinion, but it’s all about pushing all those buzz words and hyping other products.”
Agreed. Who else but developers and MVP’s would be interested in using a different platform for Access, aside from that audience? It was almost condescending
For better or worse, this is where we are now. I’ve invited Michael Aldridge to present Dataverse to our AUG Access Pacific meeting next week, December 2, 2021. It’s a chance to hear first hand and, perhaps, a chance to discuss the pros and cons with him. I hope it’s a cordial, product way to interact with him and his team directly.
More info:
https://accessusergroups.org/pacific/event/access-pacific-2021-12-02/
No doubt. I wrote this article in the hopes of getting other developers’ perspective on the subject as it is a buzz word nowadays. I truly don’t want anyone to be mad for Michael for his statement! He has actually opened the door for a great discussion here!
I hope I didn’t come across as attacking him either, that wasn’t my intent with this article. I do disagree with his statement, but that in no way means he is wrong. I think a lot of this has to do with perspective and sales (with the Ignite session he was trying to appeal to a global market).
It would also be nice to get his vision of where he would like to bring the product in the coming years. Is he wanting to make the product more low-code/no-code or give us even more programming power?!