subVI expected to be at...was loaded from... LabVIEW 7.1

[GabrielaK]

Hi,
when I open VIs which were developed under LV 6.0.2 with LV 7.1, the following warning appears: "The subVI expected to be at "(my development directory on my R&D computer)" was loaded from "(new location at another computer)". Of course, when distributing driver sets, I don't want to see our customers the directory structure of our R&D computer when opening the VIs at their computer for the first time. Also, I don't want to open each single VI (from about 200) to change the subVI path information before copying them to another PC. How can I avoid that message?
Thanks in advance,
best regards,
Gabs

[GerdW]

Hello Gabs,

try to use library files.
If you put all subVis in one library, then this message should not appear. For a customer distribution this should be the solution.

Best regards,
GerdW

[GabrielaK]

Hello Gerd,
all sub-VIs are already organized in libraries. The message appears when a main VI is opened which uses these sub-VIs. Do you or somebody else have another idea?
Best regards,
Gabs

[EdDickens]

All this message means is that the path the subVI was found at last time the Main VI was saved was found at a different location. If you save the Main VI, you should not get that message anymore. Also, since the VI's were originally delveloped in 6.0.2 and you are now using 7.1, all the 6.0.2 VIs have to be recompiled to the new version each time you open them.

What you should do make a copy of all your VIs as a backup, then open them in 7.1 and save them. The message should be gone.

If you are distributing these as an executable, you won't see this message because everything gets packaged into a single .exe file, so there's no searching for the subVIs.

Ed

[GabrielaK]

Hi Ed,
we do not distribute the VIs as aexecutables, but as LabVIEW libraries. Of course the message will be gone when the customer saves the VIs. My problem is that I neither want the customer to see the relative path on my R&D computer, nor want to get him confused by these messages. Also, I cannot recompile the VIs under LabVIEW 7.1 myself, because we distribute the libraries as LV 6.0.2 libraries to make sure that customers who are using LabVIEW 6.0.2 or 6.1 still can use them. How can I avoid that this message appears when the customer opens the VIs for the first time?
Regards,
Gabs

[GerdW]

Hello Gabs,

in this case: transfer to "customer-ready" library to a computer with a fresh installed LabView/just having the runtimelib and run the program there. I think this could be useful anyway to check proper function of the program in an environment different to your development system (like: checking filesystem independent filepath...).
Best regards,
GerdW

[GerdW]

Hello Gabs,

again to make my thought clear: save all subVis in ONE library using LabView 6.0.2, transfer to a different computer (as described above), open the main Vi, "recompile", save again. That should do it.

Best regards,
Gerd

[EdDickens]

I think your best bet will be to save them as libraries as suggested, but also include the vi.lib files in the library. This might do it.

The reason I suggest you try this is it seems many of the vi.lib files have changed their location during version changes, and that is what will trigger the message. As far as I know, there's not a way to surpress the message. Maybe somebody at NI knows of an ini setting that can be included to do it.

I'm also curious as to why you do development in 7.1 if you the applicaiton needs to support distributions back to 6.0.2. Personally I would do it the other way around so I wouldn't accidently use a feature that is only in a newer version. Plus you wouldn't have to go through down conversion process if
you make changes.

Ed

[PJM_Labview]

Hi Gabs

You could Make an installer VI that do the following:
1)Copy your llbs and main to the target directory
2)Mass compile the target directory (This will relink your VI properly)
3)Run your main
4)Unload (and disgard) the installer

PJM