A family of Microsoft relational database management systems designed for ease of use.
To safeguard your database in future You might like to take a look at BackupDemo.zip in my public databases folder at:
https://1drv.ms/f/c/44cc60d7fea42912/EhIppP7XYMwggESpAAAAAAAB3aLXYo7DdARg01KnQIyoLg?e=fASl3m
Firstly, this little demo file assumes that the database is split into separate front and back ends. Even in a single user environment it is strongly recommended that an operational database be split, with the back end containing the tables only, and the front end containing all other objects, along with links to the back end tables. In a multi-user environment splitting the database is essential, with the back end being installed in a location on the system to which all authorised users have full permissions, and separate copies of the front end being installed on each user's local machine.
The demo allows backups of the back end to be made from within the front end to two locations, e.g. an external drive and a cloud location such as OneDrive or DropBox. It also includes provision for restoring the data from either backup.
The front end should also be backed up of course, but this will only be necessary if any design changes are made, whereas the back end should be backed up very regularly. With my own financial databases for instance I do so after each session. It only takes a few mouse clicks, and ensures that my backup data is always up to date. If the database accesses any external files, e.g. image files, the paths to which are stored in the database, then provision should be made for these to be backed up also.