I have found the following problem with LabVIEW 7.0. This only occurs
when running the application as built with the application builder and
does not appear to be a problem in the development environment.
Given an open refnum for a config file one can loop through several
read key operations while passing the data and the refnum to outputs
on the for loop. If you disable indexing on the refnum output of the
for loop you should get a usable refnum out. What happens instead when
you try to close the refnum is an error indicating that the refnum is
invalid. If you simply route the refnum around the loop avoiding the
for loop output altogether this doesn't happen. It appears that
somehow, going through the indexing output of the for loop invalidates
or changes the refnum when in a built application using the runtime.
If anyone can reproduce this or prove me wrong it would be helpful.
This bug cost me days of chasing down why my "major app" would only
work when in development but fail when built. The lack of debug
capability in a built app of course leant to the effort that it took
to track this down.
Thanks,
