Well keeping track of multiple sub Vi's and its dlls is indeed a messy job if right care is not taken.
we have had our share of misery in similiar situations before getting things right 😉
try following to make things easier.
- try to save your Main VI and its sub VI's a development distribution (*.lib) from 'save with options' in file menu.(also check selected options column while doing this)
- as much as possible keep renaming any changed sub VI's so that they do not clash with unchange ones if they are used by other VI's
- Delete any obsolete or unused Sub VI.
- always avoid opening two main Vi's that use sub Vi's with same name(unless they are sharing the same version of the sub vi from the same location)
For ex: if 2 main VI's A and B use two diferent Vi's that have the same name 'C'
opening B along with A will open the sub vi C which originally is a sub Vi of A instead of intended VI.
But Labview will inform by a pop up msg that this sub vi which was expected to be at location x has been opened from location Y,
Just heed to all those pop up messages and life will become easier.
One final note: while closing a VI, if save changes msg pops up, do select 'explain changes' and try to ascertain which sub vi has changed before selecting 'save sub VI's' option.
and Finally keeping a cool head is trick 😉
regards,
Dev
