Joernh

@ didierj thx, that's a good idea!! @ Phillip Brooks maybe i have to deal a little, but right now they don't like accepting characters by the numerics...... To set the data range is not the solution, because for my app it's definitely not good to coerce a value to any limit. Therefore i check the range "manually" in an eventhandler. If the value is out of range, i show a messagebox and then set the numeric to the old value. Regards Joernh

Hi everybody, i have some problems with numeric fields. I dont't want it to accept any characters, but whatever i've done, it was possible to type in the abbreviations for the SI-prefixes (like k for kilo). :headbang: Does somebody knows how to resolve this? Regards Joernh

Hi Joe, maybe there's a difference between 7.1.1 and 7.1 im deutschen manual f

....nevertheless, independent label and tab caption are properties described as not changeable during runtime (at least in the german manual), but maybe its a misstake. Thank you all for replying..... :worship: Best regards Joern

Hi Wolfram, your example confused me since both properties of the tab-control are described as not changeable when the VI is running. But it works...... :headbang: so...thank you

thanks a lot. Think you hit the nail on the head.

Hi there, can anybody acknowledge, that it is not possible to change the names of tabs programmatically during runtime?! My attempts failed. I'd also like to know if it's possible to add or remove tabsheets? Thanks for Reply Regards Joern

Thank you very much Rolf, your explanations seem to hit the core. I will think about.... ...unfortunately, it seems that not only the UI-thread is locked or even panel-independent parts of code is also executed in the UI-thread. I have a parallel while loop with a SubVI-call (parallel to the dongle-check). In the VI settings of the SubVI I chose a different execution system so far... The execution of this loop definitely stops during the dongle-access even though it is independent from the panel....... Regards, Joern

app hangs while communicating with an ActiveX-Object Hi there, is there anybody who can help me to understand why my application freezes while communicating with an ActiveX-Object? I've just added a parallel while loop to my main application loop. In the added loop i do frequently access a dongle via its ActiveX-Component and it works fine, but.... The duration of the dongle-access is about 600ms and during this time, the whole application is hanging....waiting...sleeping.... even the frontpanel. I thought that, because the ActiveX-Access is in a separate while loop, my application would not be influenced like that. :headbang: Is this a "normal" behavior of LabVIEW or where's the problem ?! Best regards Joern

thank you Michael, do you know, if there's another chance with LV6.0 to get a multiple launchable application? (except making copies.... )

Hi there, does somebody know, if this is working with LV 6.0 too. I tried it but it didn't work. I can only run one instance of the application.exe :headbang: Could somebody help me?! Regards...