Travis H.

Just as a heads up, make sure you read through the readme as the LabVIEW 8.5.1 maintenance release is different than previous maintenance releases. I'll let you read through the readme for all of the details, but here are the high-level points: You cannot have both LabVIEW 8.5 and 8.5.1 installed simultaneously (this is the same as all previous maintenance releases) LabVIEW 8.5.1 can be installed with or without LabVIEW 8.5 currently installed (this is the same as LabVIEW 8.2.1) LabVIEW 8.5.1 does not automatically recompile VIs saved in LabVIEW 8.5 upon load (this is different than all previous maintenance releases) Of the 204 bug fixes, 19 of them require a VI recompile to activate the fix (this is different than all previous maintenance releases) Previous to now, all X.Y.z maintenance releases recompiled VIs upon load that were saved in X.Y. This caused a lot of headaches since it was more or less required to mass compile your VI directories containing not only your source, but also VIs installed by drivers, toolkits, and modules. We were able to avoid the recompile upon load in LabVIEW 8.5.1 as none of the 19 bug fixes requiring a recompile were deemed as showstoppers. Unless you suspect you are encountering one of these 19 bugs, a recompile is not necessary. Remember, any further edits on a VI will trigger a recompile and enable these 19 bug fixes for that VI. If you think there is a chance you are currently encountering one of these 19 bugs, a recompile is recommended. You can recompile a single VI, all VIs in memory, a static VI hierarchy, or a directory of VIs on disk (instructions in readme). If you don't want to have to think at all, you can recompile all of your VI directories (excluding vi.lib VIs installed by LabVIEW), making the install process much like the LabVIEW 8.2.1 maintenance release. Hopefully most users will save time by not having to do this. Note, vi.lib is already recompiled for LabVIEW 8.5.1 (just like it was for LabVIEW 8.2.1). Hope this helps, Travis H.

This was reported to R&D (# 3QPET23Q) and was fixed in LabVIEW 8.2. Note, NI was notified of this by AutoMeasure's post to the NI Monthly Bugs (October 2005) discussion forum post. Thanks! Travis H. LabVIEW R&D National Instruments

Hi Guys, This is a very significant bug. Fortunately, there is a very trivial workaround. If you're using Dan's original VI, change the constant to a control for either the "element" input on the second (size of 8) Initialize Array primitive or the "new element/subarray" input for the Replace Array Subset primitive in the 1..12 case. If you're using the simplified VIs provided by Joe, then use the same concept. Change the constant to a control for either the 2-element array or the "new element/subarray" input for the Replace Array Subset primitive. This has been reported to R&D (# 3VM99T3G) for further investigation. Take care, Travis LabVIEW R&D National Instruments