I developed an application in Labview 8.6.1 that controls a test set using a DLL devolped by someone else. The application works great in 8.6.1 but we are now trying to move to Labview 2013 and things aren't as nice when I move the application to this newer version. The application operates as such: I have a DLL inside a queued MHL to which i send messages from other loops. I initialize the DLL with the location of a file (xxxxx.doc) and then and then write the IP address of the test set to the DLL. If everything is ok I can continuosly communicate with the test set without having to resend the location of the file or the IP addres and thats how it works in 8.6.1, but in 2013 it looks like Labview drops the DLL from memory with each message to MHL and i have reinit the DLL anytime I want to communicate with the testset. How can i prevent this from happening if this is the problem or whats else could it be? See the attached image for a simplified version of my block diagram.