Hi Rene,
What I think John means, is that there is a rule set for developing Rhino that explicity states that no files are changed when they are not ‘opened’.
If you allow Rhino to change files that are not open. There are many things that can ho wrong. For example 2 instances of Rhino could try to change the file simultaneously.
The way this is solved for blockedit of linked files, is that the block file is opened in a new instance of Rhino to be edited in.
I think what you need can be scripted but it is not straightforward.
Does this help clear things up?
-Willem