That all depends on how big the database file is and what kind of Internet speeds you have. Since YOU are the ONLY user, you could use a Cloud backup solution like Google Backup and Sync, Dropbox, OneDrive, etc. to copy the file back and forth. If it's relatively small and your Internet speed is decent, this might work for you. This is NOT a solution if you share the database with other people. In that case, see Access on the Web.

Everything you put in your Google Drive shared folder will show up on both systems. Now, if your database is small enough, and your Internet speed is fast enough, and your commute time is long enough (a lot of variables, I know) then by the time you go from the office to home, the file should have synced up. If you've got, a 100 MB file, Gigabit Internet, and a 20 minute commute, you're good to go.

I would suggest copying the file OUT of the Google Drive folder to your desktop to work on it because Google will keep trying to sync the backup and if the file is open, that's not a good situation (see Backups). Then when you're done, copy it back. Optionally rename it so you've got the last 3 or 4 copies (rotating backups) saved and you know which one is the most current and that it indeed copied over.

Hope this helps, and I might mention this in the next TechHelp Quick Queries video.

Thank you, Richard,
Right now our database is small, with 21 records, but I wanted to get a handle on all the options of developing a realist table.  Sometimes it comes to me or my while at work by the time I get home it's not the same.  Looking forward to seeing it on TechHelp.

Mr. Richard Rost
will installing NAS drive like synology in the office will solve the above problem ? I mean; will shared hard drive which - I think - can be accessed from out side the company - NAS Drive solution - solve the problem ?

A NAS drive, external hard drive, thumb drive, ANY kind of drive is just fine in your office, on your LAN. The problem is that as soon as you start using that drive over the Internet or any kind of remote connection your latency goes WAY up. Access by itself is a FILE-based database. It needs QUICK response times. If your connection is slow you're GOING to have problems. SQL Server is a client/server-based database. It can deal with high latency. Bottom line is: unless you are the ONLY user, I wouldn't recommend it. You start dealing with multiple users and high latency, you're going to have a SUPER slow database at best, and corrupted files at worst.

I would definitely NOT connect directly to the Access database using a VPN. A remote access solution like Chrome Remote Desktop or pcAnywhere would work fine. This is where you are connecting to a workstation in your office. Only the screen display info and your mouse clicks / keyboard typing is sent over the wire.