This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have developed several applications on Microsoft Access using Dataverse as the source tables. This works very well but the main drawback is that I have to create Front end files and install them on multiple desktops. This can be a challenge to manage updates. I would be very handy if I could replace the Access front end with a cloud solution so, users can easily use the app on their browser. I am looking at Microsoft Forms for Dataverse tables, but I don't see a way to connect Forms to Dataverse. Any ideas?
A family of Microsoft relational database management systems designed for ease of use.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 41%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETV%3C/text%3E%3C/svg%3E)
Apps usually abandon CRUD pretty quickly, and logic becomes more important. So one option is a quick cheap Access FE to that data with VBA logic, or a .NET web app with all its overhead and costs. Is there anything in the middle?
re:need tools requiring minimal coding and learning time.
with the AI like Copilot help,many codings can be finished without difficulties.
Hi Grover,
I am familiar Power Apps. Unfortunately, I don't have the time to invest in the steep learning curve required to use it. As opposed to Access, I also find the Power Platform environment incredibly unwieldly and complicated. Developing and deploying apps using Access is much faster than Powers Apps. Access allows for the creation of queries and reports in one environment. And easily customizing a Power App? Good luck with that. Furthermore, the hybrid Power Apps environment, what I call pretzel logic, with confusing GUI's, makes it nearly impossible to create anything useful without deep programming experience. To be clear, I am not a software developer. I am an Access Database developer. And that is the huge difference here.
Access is a tool that citizen developers like me can use with a reasonable learning experience in a reasonable amount of time, something Microsoft is woefully out of touch with. Whoever developed Power Platform doesn't understand the exigencies of medium to small businesses or, in my case, a nonprofit. Busy, overloaded staff, i.e., citizen developers, need tools requiring minimal coding and learning time. Microsoft, touts Power Apps as a low code/ no code platform. Sure, you can create an app from a spreadsheet or an SP List and create something like an employee directory via drag and drop but the low code side is anything but! And this is why upwards to 75% of staff at organizations that have Power Platform licenses don't use the application. It is just too difficult to use. In this regard, Power Apps is not a very useful tool.
In any case, I found the solution I am looking for and, ironically but not surprisingly it, is not a Microsoft solution.
Although I agree with Tom's comments, I would also like to point out that the "browser" based solution you might want to implement could be in PowerApps, not MS Forms.
Licensing costs are a significant factor, though. It might bear investigation nonetheless, as would be the case with other solutions.
> This can be a challenge to manage updates.
It doesn't have to be.
In its simplest incarnation the BE has a table with CurrentFEVersionNumber and if that does not match, you bitterly complain and direct the user to update their FE,