I do believe your story. But I'm sure he didn't get those VI's from NI. He probably got them from whatever company supplied the instrument. If you look through the instrument driver network or any third party company websites that supply LabVIEW drivers for the devices they sell, you will notice they are notoriously bad. They are usually ancient (such as yours which was in LV 5.1) They never bother to fix any issues or update them to newer versions. (If any company is supplying a 5.1 driver, they should have long since upgraded to at least 7.1). They use a ridiculous amount of stacked sequence structures and local variables. They also use code constructs that would be a highlight of the Rube Goldberg thread.
I had one driver (not sure I ever posted it to the thread) where they took a 2-D array, used 16 index arrays with constants 0 to 15 on each one. Bundled those 16 values into a cluster. Used cluster to array to get an array. And this construction was used on half a dozen such arrays. First, you can use a single Index Array, and get 16 outputs. The travel to cluster and back was completely unnecessary. For what they were doing, a single Index array with a For Loop around it and the i terminal wired to the index was sufficient. I'll have to say there wire was neat, but the weird way they did things used up 15-20 screens of space instead of the 2 I narrowed it down to when I cleaned it up.
I'm not trying to say you are wrong about the source of your code, but the fact is you were so narrowly focused on this being an NI piece of software installed with LabVIEW, and not the work of the one guy before you who was the only one who touched the code, that you weren't at all thinking about the possibility that the one guy got the files from somewhere else besides NI. Because of that narrow focus, this thread dragged on far longer than it should have and delayed giving you the help you needed.
