@PaoloDeLeonardis
Keep in mind that a relational database application is composed of three main tiers, or layers.
- The data layer. This is the set of tables in which all data is stored. Access tables, of course fill this role, but many other database engines exist: SQL Server, SQL Azure, MySQL, Postgres, to name a few.
- The interface layer. This is the set of forms and reports through which your users interact with the data.
- The logic layer. This is the code (and in Access, macros) which provide the logic needed to manage both the data and the interface.
Access is quite unique in that it includes all of those objects and tools. Most other development environments include only the 2nd and 3rd, leaving you to choose a database engine appropriate to your needs.
However, Access does not limit you to its own proprietary database engine (which is called ACE by the way). Access can connect, or link, to a huge range of other data sources, including those listed above as well as SharePoint lists, text files and Excel files. This means that any data storage you choose can be the data layer for a proper web app, and that Access can ALSO link to it to provide an in-house desktop interface.
The next thing to consider is that whatever interface tools you select will come with their own learning curve, greater or lesser depending on what you choose. Things like .net or php which are needed for a browser based interface may be more or less challenging to you, in other words. Again, depending in part on your skills and aptitudes, you might be up and running fairly quickly, or not. One thing you should NOT consider, though, would be to use Access tables as the data layer for other interfaces.
And finally, I would like to offer the observation that Access is a tool used to create one specific class of relational database applications. I would probably approach the task as looking for other tools to SUPPLEMENT, not to replace Access in your tool kit.
