Yes, you certainly could. You could connect your Access Cloud DB to your existing SQL Server, OR you could install SQL Server on the Cloud PC. In fact, I'm going to be putting together a video on how to do this in the near future.

Thank you very much. I'm looking forward to this, as it is urgent for us to speed up our database, which is quite big, especially the order form entails a lot of routines, thus it quite heavy for transferring data over the wire.

I may consider, but for now, I have set up an old school batch file set to run at Windows Startup, to set a "local" drive from my One Drive account that is working for my individual needs. Setting up by traditional "Map Network drive", Access balked for linking the Backend files;  as a "local drive", it works just fine. Interesting.

I ended up finding the guide on Tech Republic via a DuckDuckGo search.

Base code: subst y: "folder path"

Brian -
I disagree and feel this is not good advice.
You need to reconsider using OneDrive as a local folder.  You might get away with it for awhile but eventually you WILL corrupt your database.

OneDrive is great to store your backups but DO NOT use it as a means of sharing your database.

See the Access Online page and video.

Brian, again, I strongly recommend against that. See me Access Online page.

See: File Sharing

See my comments in the other thread about this. If you use Google Drive's Backup & Sync Windows App it will automatically set up a G: drive for you. No need for batch files. I prefer it over OneDrive or Dropbox.

Scott and Richard:

I **am** a one man operation, and have *no need* to share my databases with __anyone else__ over OneDrive, only sharing results via Reports and Excel Workbooks as needed for tax purposes.

I recognize your disagreements, as it's not a good general practice to use the batch I referred to above, and that's fine, especially when 2+ users are potentially using the same database; in-/outside the same local network. In the short run, it serves my needs. And yes, the DBs could get corrupted, regardless of source location. However, thus far 3 coming in at under 2 MB ea, as split backends, they are easy to restore with backups. I don't see them going over 3-6 MB ea by end of year.

Yes, I have my own servers, and can work on moving it online, but for now, Workbook entry, and as-needed table "append" from Workbook links do the job for my current learning curve.

I hope this helps.