Access Online

Most NAS *don't run Windows.*  That may be okay for files, but Access is not just a file, but a piece of software, made to be run on Windows no less.  So it needs to be put in a Windows environment in order to run at its best.  So I advise against putting Access back ends on an NAS.

Most NAS use custom-made OS based on Linux or other open-source OS, because they are free and Windows isn't.  Connecting an NAS to a Windows PC is like connecting your Android phone to your Windows PC: you can see, copy, and paste the Android files using your Windows Explorer as if they were part of Windows.  (Android is also a free and open-source OS, by the way).  But you wouldn't put an Access back end on your Android phone, the same way you wouldn't io an NAS.

In the "Access Online" video that Adam mentioned above, Richard also advises against using Google Drive or the likes to store Access back ends.  The reason is similar: Google Drive likely doesn't run on Windows either (most likely Linux).

Richard recommends using MS SQL Server for a database backend and using MS Access as a frontend on the user's computer (splitting the database). I'm exploring using MySQL (on a hosted web site) as my backend, and so far it is working well, and using MS Access as my front end on various user's computers, here in the office and on remote sites (sublet vendors and job site users). I think it will work out well. I used ChatGPT (suggested by Richard and other site posters) to help develop the connection code.

As the previous comments have already suggested, I wouldn't use a NAS with Access. They work by transferring changed files (or pieces of files) over the wire in a way that doesn't mesh with Access. Unless your users get a DIRECT connection to a drive on that NAS (and not just a cloned local copy of it) then I wouldn't trust it. And even if they do get a direct network connection to it, the performance over the Internet is going to be TERRIBLY slow.