Hello, I=92m glad to hear you found a workaround for this issue.
There is nothing you have done wrong in your program to cause this. There doesn=92t have to be any relationship between the strictly typed VI and the VI which is throwing the error. The error can actually be replicated by two independently running VIs. Our R&D engineers are currently working on this issue. Ken S. National Instruments
