One thing the new MS 365 universe has that did not exist with Access is that all of these apps and functions can be turned on/off for users by admins. So if you are in your team in MS Teams and you don't see Power Apps, it's probably because your admin decided to turn it off for you.
We don't have control over the Office install at work, so it's 2019 x86-64 bit.
Declaration was modified with PtrSafe and a new .accde was generated and we were good to go. But as mentioned, the 32-bit clients need an .accde that was created in 32-bit Access.
Using SQL Server as a back end requires more than the standard MS 365 Business license. Your options are:
Per app plan
(Run one app per user)
$10 per user/app/month
Best for businesses that want to license each user to run one app at a time, with the flexibility to stack licenses for each...
It certainly looks promising, but at the same time I worry as developers who really know Access, we may find some limitations. I have to be fair because I haven't tried it yet.
SQL Server.
Front-end on each (work at home) computer and back-end in SQL Server.
That is a problem. MySQL...