Hi Ben, thanks for your answer and the interesting link. But I think I have the direct inverted problem to yours: You had the problem that a dll called from VB runs in a different memory space than LV, so you have no direct access to your LV application. But my problem is that a dll called from LV runs in the same memory space so that subVIs are recognized where they were loaded first. But I would appreciate a behaviour that the dll only knows its own instances of subVIs and the top level application uses second instances. But obviously this is not so easy in this configuration. I will take a look, like you have done on "SubVIs in Memory" and "First Call?". This is a good hint. Maybe this will help me to procced with the problem.
I will keep you informed, but everyone feel free to post any other ideas... Michael
