Forum Discussion
Moving Away from MS Access
The following online database software are structured like Access
- https://www.hyperoffice.com
- https://www.caspio.com
- https://www.zoho.com
I'm not sure what "structured like Access" might mean.
Any relational database application requires three components:
- A Data Layer: the tables in which data is stored.
- An Interface Layer: the forms and reports through which users interact with that data.
- A Logic Layer: the code which automates interactions with, and manipulation of, both the data and interface.
All relational databases work this way, so "structured like "Access" might mean only that these products have those three components. Perhaps your intention is to suggest deeper similarities?
Of the three mentioned products, the only one I some knowledge of is Caspio.
To use Caspio you must first migrate your data out of Access tables into Caspio's proprietary database, hosted on their site.
Then, you open the Caspio developer site and create new web objects (screens, code, etc.) to interact with the data.
You can continue to use ETL approaches to pass data back and forth from a local accdb to the Caspio tables, but that's not an intended scenario.
I suspect the other two products approach their solutions in a similar manner.
To properly evaluate them as alternatives, it would be very important to decide what your organization requires from your relational database application, and then independently verify how, and even whether, those alternatives provide acceptable features to meet those requirements.
It's essentially a one-way street, so be sure you are ready for that before you plunge in.
Are we still discussing Access? Sounds like very serious proprietary app used for Big 500 with Terra bytes of data.
Here, while you guys still thinking what is possible or not, I've moved 100 tables with POC data for the customer, and build the App in about 5 hours. ETL? My goodness, what is seen is a production data for a small company looking to migrate. None ETL was needed in a sense of manual work. All table and fields Captions preserved in the DB, all ~1300 of them.
Ridiculously easy. ZERO CODE, except wip Dashs! This is probably the first and only app seen on Arabic language for many - myself included.
https://arabic.pythonanywhere.com/
How to move Docs:
https://jampyapplicationbuilder.com/tips/migration/examples/index.html
This thread is now going into a third year. I would really encourage people to start learning some basic JS and ie Python.
Hi all,
to make this move easier for everyone, a lot of SQL from MS Access is a problem for non-skilled would-be devs out there - like myself.
So, have you ever considered using ChatGPT for moving ie Reports SQL from Access?
Here is a large Reports SQL converted by ChatGPT, if asked nicely 🙂
Used ChatGPT on many occasions, sometimes it's wrong, sometimes is 100% correct.- ChatGPT has its uses as a tool for getting you started, but relying on it to produce accurate results is dangerous. It frequently returns queries which mix syntax from multiple versions or even multiple platforms.
If you are not able to read the output code and verify that it looks reasonable, don't put it in production.
- > It's essentially a one-way street, so be sure you are ready for that before you plunge in.
Hence you start with a pilot project, and migrate a small percentage of the app. I probably would worry less about the data than the ability to create forms with identical functionality.
