11-21-2006 10:37 AM
11-22-2006 08:28 AM
Hi Mathieu,
If you have DIAdem 10.0, I'm afraid you're stuck-- there was a bug of this type introduced in 10.0. The good news is that it didn't exist before 10.0 and it has now been fixed in 10.1, which is due to release in a couple of weeks and is also available as a Beta version. If you are using some version other than 10.0 and still see this problem, then let us know (and send us your VI)-- we should be able to change your code to make it go away.
Regards,
Brad Turpin
DIAdem Product Support Engineer
National Instruments