The company I work for uses a central server that syncs to Google Drive, that every computer has selective access to. Tasked with building a parts database, I've been working in Access 2007, saving the database to the network drive. After a week or so, the database started to become corrupted. Every time I opened it, a warning message came up saying the database is in an inconsistent state, and needs to be recovered. This was odd, but worked for another few days, until saving individual tables or objects in the database refused to save, saying the database isn't a valid file format. I searched online, and it looks like the most common cause of this error message comes from opening an Access 2007 database in Access 2010, but that isn't what's happening here; I'm just using the database under normal conditions. Now, the database won't open at all, saying the file cannot be recovered, and that the file is currently in use—which is odd considering the file isn't open on any other computers. I tried to rebuild the database just to see if it would come up again, and sure enough, after just a few days, it started to become corrupted.
Maybe Google Drive doesn't play nice with Access? Does an Access database use invisible files in the background, which Google Drive is syncing separately to and from the network server, causing some sort of file disparity?