Forum Discussion
Migrating Access back end to the cloud
- Do you want to run this relational database application as a web - browser based application, or as a desktop application?
I don't know which "guys in India" you mean, or what they recommend, but you really don't need a lot of other software packages if you are going to continue to use this as a desktop application. However, if you want to replace the Access interface with one that will operate in a web browser, you WILL have to invest in and learn to use the appropriate tools for that.
So, start by explaining who will actually use it, where they are physically located (in a single facility or dispersed among several) and how you anticipate using this relational database application. From there, we can examine some options.
And what exactly is the viable alternative to bringing Access to virtually any mobile device?
At the risk of starting another whole new tangent, you might want to look into PowerApps.
They do require an MS 365 subscription, and the interface design can be challenging for Access developers who've not explored other software development tools. But if you are willing to add the cost of a VPS to the solution, then the cost of licensing for a PowerApps alternative might also be considered affordable.
To be honest, I'm more interested in exploring alternatives than staking out territory and defending it against alternatives. Therefore, I'd always suggest that people who need to move away from a traditional Access desktop configuration take a broad look at whatever seems feasible. OneDrive and DropBox, and similar services, can and should be considered, but as soon as their limitations become apparent, they can be put to the side and reserved for that rare niche where a single user is involved.
All other options need to go into the matrix of features, functionality and cost for consideration. We do our best service to clients when we make a serious attempt to evaluate their needs against ALL available options.
There is no single right solution for all purposes, we agree.
Power Apps I looked at the AEK. As a replacement for Sharepoint lists this may be sufficient (but way too expensive for the purpose).
To bring an existing Access desktop application to a mobile device, this is unsuitable from my point of view.
Karl (Donaubauer) knows my view on this and he also knows the planned implementation of deploying our Access based CRM and document management application to the smartphone.I personally don't see PowerApps as a replacement for anything, really. From the perspective of the Access developer, it's only a tool that allows us to extend appropriate functionality from the Access desktop onto mobile devices. I did a presentation Thursday for the AUG España chapter. I made this the central point of my presentation, in fact. It makes no sense, to me, to try to replicate what an Access desktop application can do simply because you want it to be available on a smart, or mobile, device. However, some functions do make sense. Any time you can send an employee with a mobile device to where the raw data exists and have them collect the data at that location, that would be a candidate for a mobile app that does that one function. Hence, the form factor required for a full-blown Access desktop application isn't an issue.
With regard to expense, that remains, IMO, the single biggest barrier. I have a per user/per month plan, which costs me ~$22.00 US every month. However, that allows me to create multiple PowerApps applications. To add one single user would duplicate the cost under that plan. It's a hurdle most small organizations can't overcome.
I'll be fascinated to learn more about putting a
CEMCRM and document management application on a smartphone. That sounds challenging.I talk to Karl regularly. He was responsible, in fact, for sparking my interest in PowerApps again.
- In my opinion, the Power Apps were developed for large companies and corporations and can be used sensibly there.
For "small" brings but little.
Last year I started adapting our Access CRM to smartphone use. I am currently using it (for the time being only for myself) on my Android smartphone.
In principle, DokuWork Mobile (planned brand name) replaces the need to operate an online exchange account in order to provide mobile calendars, contacts and emails across users "in time".
No matter who enters what in the office, the mobile user sees it immediately (and vice versa).
In the final development stage, the projects, documents and the entire invoicing are then also ported to the smartphone.
As soon as I can accommodate that in time, I'll create a PDF with screens that describe the functionality.