As mentioned by others, looking at the "current changes" in any VI just opened, it shows:
(a) The fact that it was converted, e.g.: "VI converted from a different version of LabVIEW" (b) What the previous version was, e.g. "The VI, last saved with LabVIEW 6.1, has been converted to version 7.0." Obviously, information (b) is readily available internally. For completeness, it should be available programmatically, exposed via a VI property. For me, it's a "surprise" that it's not. ;-) In can think of many uses for this, especially for code maintenance, e.g.: -- A tool that quickly shows name, last saved version, revision number, etc. of all VIs in memory. -- A tool that searches a file system for duplicates, then lists them as above. -- A masscompiler that does not touch VIs that are more than one versions older than the current release. -- etc. I agree that the method I showed is probably flawed, but it would be nice to be able to write a little tool such as this without the need for jumps through flaming hoops. -------------------------- Back to the original question of this thread. For future projects, I would recommend to just arrange the VIs into folders where the name contains a clue to the LabVIEW version, e.g. /../customer1/application2/6.1/... Remember, since the customer has his own LabVIEW version in this particluar scenario, he might independently upgrade for reasons unrelated to your application.
