Insane object error(The string control not getting any values)

[Kodeeswaran]

 

In LabVIEW 8.2 i am using the string control to get the text from the users, and initially there was no problem at the time of development it works perfectly, after building the installer,

these string controls are not getting any string input, it seems like a disabled one, but actually it was not disabled, when we try to click over that through the mouse,

 that text inputting cursor was not blinking over there,I screen looks as below, some error messages are thrown from the LabVIEW like insane object error, even

now there was the same problem in the source code itself, what to do rectify this. Only this part generates error all other remaining screen panels are working perfectly.

[mikeporter]

This kind of problem can be a pain to locate. This often occurs when the wiring to or from a control or indicator is bery long, convoluted and hidden inside of structures or behind things. So first, you need to identify which VI specifically is generating the error by individually saving VIs and subVIs until you find the one that is generating the error. Now try and remember the last time that VI saved without a problem and what edits you made since then. Places where I have had this occur was when I drag-copied a control and a couple VIs into a small structure. Sometimes the wires would seem to conect up properly, but when I tried to save the VI I got this error. The solution was to disconnect all the wires associated with the VIs I had copied and rewire them.

Also, can you post the VI that is doing it? Shouldn't need the subVIs for this...

Mike...

[Kodeeswaran]

thank you mike,

 i think this might work, if i made corrections what you said, i will get back you after doing the same.

[Kodeeswaran]

 My string control was developing problem, that i could not type or enter any values in the string control. i rewired all things and didnt see any solutions,

what could be the possible reasons.

[mikeporter]

Can you post the VI that is showing the problem?

Mike...