03-02-2007 09:27 AM
@Kravlor wrote:
... Is there some sort of mailing list we can be put on to find out when the official fix is released?
04-10-2007 04:20 PM - edited 04-10-2007 04:20 PM
@Kravlor wrote:
... Is there some sort of mailing list we can be put on to find out when the official fix is released?
LabVIEW 8.2.1 (which has a fix for the above problem) has been released. If you are on subscription service (SSP), then you've been shipped the new release automatically. Does that count as a mailing list? 🙂
Refer to the following link for more information:
LabVIEW 8.2.1 for Windows - Compatibility, Bug Fix and Upgrade Information - http://www.ni.com/support/lv8_21.htm
Enjoy,
Roy
P.S. - We discovered a problem with upgrades after the release. It's trivial to fix, once you know about it ("once you know about it" being the key phrase). Please read the online version of the Upgrade Issues (via a link on the above page) before you upgrade (to learn about this problem and any others we learn about).
Message Edited by Roy F on 04-10-2007 04:39 PM
04-11-2007 12:07 AM
@bww wrote:
Just to follow up with my previous post, the work around that I suggested does in fact work, atleast for my application. Please see attached vi. It turns out that the crash only occurs with the table being an indicator and not a control.Regards,Bryan
NO, LV 8.2 crashes even when the Table is a control. Today morning we tested it. In our application, we use the Table as a control since the user is required to fill it with 0s & 1s for 8 signals (rows) & desired Samples (N no of colums). We saw the same error number thrown out by LV 8.2, as mentioned earlier in this post.
But anyhow, we didnt buy LV 8.2 yet... relief... !
We may buy LV 8.2.1.