02-13-2009 09:35 AM - edited 02-13-2009 09:36 AM
Here is the snapshot of the block diagram of the main VI that calls the caller of the VI in question. Hope you can catch the culprit this time.
Thanks a lot for your help!
02-13-2009 10:10 AM
02-13-2009 11:48 AM
There was a bug in the static ref when used in an exe. Try replacing the satic reference with one derived from "This VI's path" wired to a "open VI ref".
Ben