Moving Away from MS Access

jaknap 

I'm not sure what "structured like Access" might mean.

Any relational database application requires three components:

1. A Data Layer: the tables in which data is stored.
2. An Interface Layer:  the forms and reports through which users interact with that data.
3. 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.