This MSAccess tutorial follows a step-by-step approach to the creation and development of a commercial database application. That means that you have to design the database before you actually start to write it.
There are several basic techniques that must be learned to ensure that the database structure will be solid.
Suppose you have a long process in Access that is triggered by clicking a form button. Drop me an email and I will promptly and gladly rectify it.
This process does a lot of things behind the scene, such as updating records, deleting and recreating tables, or emptying tables. Document deletions such as deleting a table or report 3.
After this Microsoft Access tutorial, you may want to go on to bigger and better databases such as Oracle, SQL Server or My SQL.
A database is a collection of objects that allow you to store data, organize it and retrieve it in any way you want.
What this means is that, with MSAccess you create structures called tables that allow you to organize the data so that it's easy to find later, you create forms that let you input the data into the tables and then you create reports that print selected information from the tables.
(Using a different back-end is another, but more long-term option that is unfortunately currently not acceptable.) Most users will be read-only, but there will be a few (currently one or two) users that have to be able to do changes (while the read-only users are also using the DB).
We're not so much concerned about the security aspects, but more about some of the following issues: When you say "Using a different back-end is another ...", does it mean that you do not want to split your app into one back-end access file and multiple access clients, or does it mean that you do not want to use another solution than ms-access as a back end?