KnoWei wrote:
It would still be nice to have a text editable config file that allowed advanced users to point Coollector to a custom location for the MyCoollection.cool db file.
This could easily be done. On startup, the program would check if the advanced user has created a config file, and read the location from it. But I don't see the point to complicate when the solution is as simple as using a shortcut to the coollection file instead of a shortcut to the program...
KnoWei wrote:
This would allow the db to be in a shared location on a single computer or for it to be on a network.
If several persons modify the coollection file, of course it will get corrupted.
Even if you're the only person accessing the file, doing it through a network will probably generate corruption from time to time, and you'll have to restore your previous backup (automatic backups are created in the same place as the coollection file, in a folder named "Backups").
KnoWei wrote:
While db on the network poses risk of corruption I think this can be managed outside of Coollector on a NAS by limiting write permission to only one user ID and making all others read-only for that network share.
Indeed, that's a great idea. I'm curious to know how often the file will get corrupted, but it should be manageable.