5 ms·
Now do MS Access. But seriously, this is kind of a bummer and a lot of people are going to be left high and dry. This is like when they started messing with pai
by gonzo41 3y ago
Now do MS Access. But seriously, this is kind of a bummer and a lot of people are going to be left high and dry. This is like when they started messing with paint.
- amanzi 3y agoMS Access still keeps a whole load of orgs running (whether they know it or not!) But now you've also got Power Apps, which is kinda like the "New MS Access". So if you had sprawls of Access databases before, you can look forward to sprawls of Power Apps instead. I've already seen Power Apps keeping an important business process running, until the user that deployed it leaves the org and it just dies...
- JohnDeHope 3y agoI'd agree if Power Apps had a programming language backing it up. Say what you want about VBA, but it's at least a programming language. The databases and UIs were often just along for the ride, in my experience. The ability to run code was what made MS Access so useful to me. Power Apps just isn't there, yet, I don't think.
- nullindividual 3y agoPowerApps can call external services, such as Azure Functions.
- pjmlp 3y agoPower Apps are extensible via PowerFX, Canvas components, Web APIs and .NET SDK, or do you mean having some programing right there in the canvas designer?
- gonzo41 3y agoI was joking of course. There's just a bunch of business critical stuff where i work that runs through old access DB's and I'd love for MSFT to sunset it and force everyone to have to confront some old business processes with new eyes.
- mynameisnoone 3y agoFileMaker Pro enters the chat. FMP: I'm still alive. Paradox enters the chat. Paradox: I'm still alive too! ---- Let me regale you of tales of FMP running on 1U Xserve's concealing retail IDE PATA drives and no concept of redundant power supplies.