Has anybody else seen this problem?
I've been doing some development on a customrs PC and on mine. On the customers machine, they have LabVIEW install at
"D:\National Instruments\LabVIEW 8...". On my machine, I have it at "C:\National Instruments\LabVIEW 8...".
If I open the application on my machine when it was last saved on the
customers machine, it starts searching for my user.lib VIs, and I get
warnings like the one listed below.
"LH_Auto Controls Change__gewct.vi
- The VI expected to be at "<userlib>:\Config
File\Read Key(type and data)__distek.vi" was loaded from "C:\National
Instruments\LabVIEW 8.0\user.lib\File IO\Config File\Read Key(type and
data)__distek.vi".
Write Control Values__gewct.vi
It does the saem thing when I open it on the
customers machine after I've saved it on mine. The user.lib is in the
default location on both machines and the "Paths" options are all set
to default.
It just sems that since it appears to be using relative paths (note the
<user.lib>:\Config...) that it should know where everything is.
Is this just happening to me?
Ed