> That's because LabVIEW need a VI's wiring diagram to recompile it up
> to a higher version, and building a VI into an executible removes
> it's diagram by default.
The runtime engine doesn't have a compiler, so even if the diagrams were
present, there's no way to recompile.
> >As I understand it a version of LabVIEW can always(?) open a VI written
> >with an earlier LV version but the converse is not true.
Converse... inverse... reverse... nope, it's been too long since my
discrete math courses. Can't remember how to form logical converse.
But this is true in the development system:
* Any LabVIEW after LV4.0 [assuming no bugs in code] can always open any VI
written in an earlier version of LabVIEW, even across platforms [written on
Mac, open on PC, etc].
* A VI written in a later version of LabVIEW can never be opened in any
earlier version (no 7.0 VIs can be opened by 6.1).
* Each version of LabVIEW since 5.1 has had the ability to save VIs for the
immediate past version of LabVIEW. In other words, 5.1 could save a VI in
5.0 format. 6.0 could save a VI in 5.1 format. If you used features that
were new in the later version, then when you opened the VI in the earlier
version, the VI should open, but you may find parts of your diagram/panel
removed since those features didn't exist.
Pojundery,
Stephen R. Mercer
-= LabVIEW R&D =-
