Ken...Thanks for the quick response. The work around that I found is to disconnect the control from the strictly typed. Once I do this, the Main VI and the SubVI work harmoneously.
Rather sending you the actual code on which I was working, I was going to create a simple case of the above. I used one of the strictly typed controls and a subpanel (and inserted a simple SubVI). When I ran the MainVI and changed the value of a strictly typed control within the strictly typed cluster, I got the 1082 error. The error pointed me to a Waveform Graph property node in the application from which this problem originally came (it just happened to be running). This particular VI was the SubVI inserted into the subpanel in the original application. When I stopped this VI (but still in memory), the mockup application worked fine. The mockup also worked when I put a case statement around the waveform property node in the original running VI (essentially it was switched it out of the program). How does a waveform property node interfere with a strictly typed cluster control (having strictly typed controls within it)when there is no relationship between the two???
