This has to do with the way LabVIEW manages it application memory space.
Since LabVIEW maintains only a single reference to a VI no matter how
many times it is used, if you change one you change them all. This
includes saving because it doesn't separate out that single reference
unless you tell it to.
I think NI had to make a guess as to which way would be best as the
default action. Sometimes you want all of them updated with the new
version, sometimes not. Although I have to admit that most of the time
I'm modifing that instance because that particular one needs to be
different from the others. So maybe it was a bad guess on NIs part for
this action.
I ended up making a small utility that emulates the "
Save
a copy without updating callers" function that Paul mentioned. If you
save the attached library to a directory called 'Wizard" under your
root 'LabVIEW x.x' directory, you'll have a new entry called "Save Copy
As...". Selecting this will let you save that instance with a new name
without having to remember to check that little box in the dialog.
This is built in 6.1, but works fine in 7.0 and 7.1. Just mass compile it before you run it.
Ed

Message Edited by Ed Dickens on 10-11-2005 03:27 PM

Ed Dickens - Certified LabVIEW Architect
Lockheed Martin Space
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.