You can try the following. Install a fresh copy of Vue somewhere (standard installation) and see then how there the collections are done. And then copy this structure - if possible. When you have such a fresh installation not all the optional objects are loaded to your hard disk, you can do that when you need it. And when i remember it right, you can decide wether the object should be copied to your hard disk as well or not. I think the big problem is, that Vue tries to write back information to the .prv file when it realises a change (can't find the files in this case here). And because it can't find the prv-file as well it is confused and maybe creates a new, emty one temporarily. Only a guess. You should report that to E-on. But to be honest, my feeling is that this will be a very low-important issue to them. Not many users will have such a specific construction.Especially in times of very cheap hard disks. Broken down to the price per MB your way is probably the more expensive solution anyway. But thats a theoretical answer - don't listen to it.

One day your ship comes in - but you're at the airport.