NathanK

This issue is now being tracked by NI as bug #135766. Thanks, Nathan

ned, Connecting to the local main application instance using the method you described will work but in this case the VI server client is connecting as if it were a remote client. This has two repercussions- 1- you have to enable the vi server access and specify a unique port as you described, 2- You don't have access to some VI server functionality remotely. This is not so much of an issue if you are just running a VI. I'm sure you already know much of this but another way that you could go about getting the reference to your VI is with the following method: I had a VI that fired a dynamic event in my main application and I want it to be called from a web service. My main application happened to be in a project and I knew that project was the only project open. Alternatively you could use the property to get the main application instance (the property I don't have wired). Or if you didn't know what application instance your VI was in you could append them all to one array and search through them. Note that the VI is referred to only by name and not the full path. If you use a path then VI server will load the VI- with just the name the VI has to be in memory already- which is what I wanted. I hope that is helpful. Nathan