I run Windows 7 Enterprise and I use servers at my location to keep most of my files. I have not had any issue with this until recently when trying to store a database file type that was created with a software for my CAM system. Any time the files <which have .tooldb> as the file extension are accessed while on the server location randomly the file can become corrupt or inaccessible - at which time in the same location a supporting file is created that carries the file name and .tooldb-journal along with it, and an alarm Disk I/O Some kind of disk Error.
I can recover the files by copying both the original .tooldb and the .tooldb-journal to my local drive and simply open the original - at which point the -journal file disappears and the database opens.
How can this be avoided? Everything I can find shows that this is and SQL error pertaining to timing and capturing a certain amount of disk space on the server disk while handeling the file and if the compilation of this database in that instance does not fall within these parameters then this is a likely return.
I don't know if this is the right thing or not, does anyone have any direction here or ideas?