Agreed! I'm waiting for my corporate admins to unlock Power Apps for us and then going to have a go. They say it is coming soon.So as I was writing the original post here it appears Microsoft has been hard at work on this problem.
you need defensive code in excel as well! I've lost count of the number of times I see data where 'required' fields are left blank or fields are filled with inappropriate data - typically text in what is supposed to be a numeric type fieldIn a spreadsheet you can produce a good tool without a line of code. You just can't do this with a database. You need a lot of defensive code to make it fool proof.
I discovered an unfortunate limitation yesterday. Apparently using Power Apps via the MS 365 license comes with some limitations to data connectors, one key one being SQL server. Therefore creating a Power App for mobile use to connect to the same back end db you're using with your desktop Access db is not possible without a separate and costly "Premium" Power Apps license.Agreed! I'm waiting for my corporate admins to unlock Power Apps for us and then going to have a go. They say it is coming soon.
Interesting. That's disappointing. I'd probably be overlaying them to sharepoint lists to start with, since my company makes us suffer without SQL server currently.I discovered an unfortunate limitation yesterday. Apparently using Power Apps via the MS 365 license comes with some limitations to data connectors, one key one being SQL server. Therefore creating a Power App for mobile use to connect to the same back end db you're using with your desktop Access db is not possible without a separate and costly "Premium" Power Apps license.
I must find a workaround so I can have my desktop and mobile talk to the same db.
How much is the "premium" license, out of interest?I discovered an unfortunate limitation yesterday. Apparently using Power Apps via the MS 365 license comes with some limitations to data connectors, one key one being SQL server. Therefore creating a Power App for mobile use to connect to the same back end db you're using with your desktop Access db is not possible without a separate and costly "Premium" Power Apps license.
I must find a workaround so I can have my desktop and mobile talk to the same db.
$10 per app per user per month (one app used at a time), orHow much is the "premium" license, out of interest?
I've heard there can be performance issues when relying on Sharepoint instead of SQL, which worries me. I'm also not sure how we would create a relational database in SP.Interesting. That's disappointing. I'd probably be overlaying them to sharepoint lists to start with, since my company makes us suffer without SQL server currently.
Assuming modest amounts of data, I've had no trouble using Sharepoint lists as tables. As to their "relational"-ness, you simply enforce it in forms and code. You represent the relations with tables just like you would in Access, really.I've heard there can be performance issues when relying on Sharepoint instead of SQL, which worries me. I'm also not sure how we would create a relational database in SP
I suppose you don't have to define relationships at the table level, though I do so I have things mapped out for myself and to provide defaults throughout the database.Assuming modest amounts of data, I've had no trouble using Sharepoint lists as tables. As to their "relational"-ness, you simply enforce it in forms and code. You represent the relations with tables just like you would in Access, really.
Then it either sucks, or there has to be a LOOOOOT of configurable properties. Either way doesn't sound like a fun afternoon to me.Power Apps can't do code, though
It actually looks like they took PowerPoint and Excel and Access and blended them together. No VBA. But there are "formulas" used in a similar-looking bar as Excel. I wouldn't be able to criticize much without getting my hands on it but I know that for many, no VBA or query editor means it can't replace Access.Then it either sucks, or there has to be a LOOOOOT of configurable properties. Either way doesn't sound like a fun afternoon to me.