Steve, thanks for bringing in Judd to demo this for us. Just a couple of clicks to migrate legacy Access databases is a great feature. I work with an organization that will be able to make use of this as they migrate their data to the Power Platform.
Thank you so much for this video. Question, once I add data in the app it doesn't go directly into MS Access, I need to close access and reopen it to see the new information. Is there a way around this?
So with this linking process; does it matter where the access database is stored after migration? If it is stored on a local computer and that computer is shut down what happens?
what abou the reports ? Once I have the data synchronized with the Dataverse and from PowerApps I can make an aplication, is it possible to "migrate" the Access reposts? In my case I have about 180 reports in access. How could you migrate the reports?
Take a look at our docs below on this. It looks like you need to first join the Access beta program to be able to do this. docs.microsoft.com/en-us/powerapps/maker/data-platform/migrate-access-to-dataverse
Great question. Sorry for the delayed response. Dataverse will give you a lot more features and capabilities both on the security options and rapidly building applications with Power Apps. Hope this helps.
It is important to note that Dataverse is not compatible with MS Access. This is due to the fact that the primary keys utilized by Dataverse are not compatible with MS Access. Additionally, it is not any faster than Sharepoint, and it is impossible to use ANSI 92 SQL on your Sharepoint lists.
Hi Steve, the info in this video is great. I do not get the Dataverse option when I right-click on the table I want to export to dataverse. How do I enable that option?
Exactly, I keep on hearing how easy it is, but there is no link for Dataverse in MS Access to export. It appears you need to setup several items before this "Easy" click export to dataverse.
@@thomasjones9394 I just setup a free Azure DB/SQL and exported one major 1.7GB MS Access table to it and then removed it from access. I then created a link to the azure table within Access and it works nicely :) .. Now my database is only 688KB :). The only thing I need to do some research on is to fix the slow export of the original 1.7GB table to Azure, which was over 24 hours :x .
@@SteveWinward Hi. So are we able to append (from Access) to the dataverse table? 2gig limit was always a problem, so if I understand correctly, the dataverse overcomes this issue. ie You can keep running your old macros/VBA in Access to clean data but now append to the final LARGE Dataverse table that has much higher limits than 2gig.
@@jamiegrayson3739 Based on my experience, Dataverse trashes everything you have done in access. I tested it with several automated macros that do inserts and updates and it will work for a while and then it will stop working. AzureSql is a better option for ms access developers or a CentOs server with Postgresql
If users have substantial data on their current Access platform they will perhaps suffer some sticker shock at the monthly cost of Dataverse storage. Let's hope they do some capacity planning before jumping into this data migration.
Every customers use case will be different here. It’s a good point to be aware of costs for Dataverse storage as part of planning. I do think for most customers there are significant benefits to storing their data in the cloud versus hosting their database locally.
@@SteveWinward currently in the process of transitioning various analytics and metrics from legacy NMCI (Navy) and intranet to Power Apps Dataverse, SharePoint Online, and One Drive for business.
