Phantom54 wrote:
I received a warning message- 'ABORTING, please try again'.
This message is displayed when something prevents the app from reading the file. It assumes that it's your antivirus that blocks the access, but there's no certainty at all.
Phantom54 wrote:
This happened on all of my stations when they accessed the same file via the LAN, including the host station.
Yep, something had locked the file. Maybe a simple restart of your NAS would have helped.
Phantom54 wrote:
When I changed to a backup data base, Coollector worked as expected.
Cool!
Phantom54 wrote:
The newest (but faulty) DB is using 673KB.
I don't think it's faulty, probably you could try again with it. This locking was mysterious and probably temporary.
Phantom54 wrote:
The most recent backup (which works) is 644KB. I guess the difference in size is because one or more files in the now faulty DB has caused the problem.
Your backup is only missing the changes you made in your last session. Did you make a lot?
The size isn't a good indication. As you make changes to the database, it grows fat, i.e. bigger than necessary. When the app creates a backup, the app makes an operation to remove the excess fat and give the file its optimal size. The difference in size seems important, but it's because the backup had been optimized and not the newest database.
Phantom54 wrote:
Suggestions?
Personally I've stopped using my NAS a long time ago because I found it annoying to have some files arbitrarily locked from time to time (it was a D-LINK DNS 323).