It isn't really designed for it. If you back it up regularly you could keep this setup as you could revert in case things go wrong. I'd definitely avoid wifi access though.

I believe, but I'm not sure, that a higher robustness negatively impacts multiple access to the database.

Thanks. So setting a value of '2' might help at the cost of performance?

I also share this same MM.DB to multiple instances of media monkey in my home network, I have multiple PCs accessing it - is it designed to be open concurrently this way or could that also cause issues?

That is likely the problem, I wouldn't connect to a database over wifi. Not only will you run into this problem, but you risk database corruption: https://www.mediamonkey.com/support/index.php?/Knowledgebase/Article/View/73/0/configure-database-performance--robustness

Thanks but I've already performed a surface scan of the said disk and it returns no errors, so I really don't think it's a hardware issue.

That said I am connecting MM through WiFi to a network share, could that affect its reliability? How resilient is it to connect in this way, or should that even matter?

It generally means the harddrive where the database is located is having problems (ie. a hardware problem). If you have multiple drives you could try using a different drive for the database file: https://www.mediamonkey.com/support/index.php?/Knowledgebase/Article/View/45/0/changing-the-default-database-location

Be cautious as your drive may be failing so having a backup of important files could save in case the drive does fail.

Not sure why this keeps happening, I've had this problem occur where I get an error querying the database. I have checked my disk for any hardware issues (scanned, etc.) so I know that is not the problem, and I use this same disk for other applications without any problem as well..

Error message:

[b]"There was a problem querying the database:

Error Executing SQL statement "INSERT INTO Played (IDSong,PlayDate,UTCOffset) VALUES (14938,44021.785329792,-0.166666667)" : disk I/O error (10,10) Cancel/Retry/Ignore[/b]

When I delete the mm.db file and rescan everything in from scratch, player works ok for a couple days but the same error keeps cropping up. I even deleted the mm.db and replaced it with a backup when I first scanned in the library, no change - it's quite baffling and i don't know what to do to prevent this. Make matters worse it keeps popping up the same dialog box again and again every few minutes.

I really like Media Monkey but with a problem like this I'm not sure I can continue using it...