Ok, I looked a little closer at your msg #3. It's now clear that what's *definitely* missing from the LV 2018 installation folder hierarchy is the vi "GetTemperature.vi" in the file "atmcd32d.llb" under the "user.lib" folder. At the moment you took your screencap, LabVIEW happened to be searching for "GetTemperature.vi" and was at that moment looking in a folder related to the Agilent 34401 in the "instr.lib" folder. Kinda subtle and several of us missed that distinction.
Based further on the set of vi's that your project expects to find under "user.lib", probably most or all inside "atmcd32d.llb" (one more is seen in msg #5), I'm not so confident that a simple copy of "atmcd32d.llb" into the LV 2018 hierarchy is going to be *all* you need to do. There may be dll files or other things that require installation rather than file copying. For instance, I noticed that one of the functions is named "Add ECO for DLL.vi".
In general, things found under "user.lib" are*not* part of an NI-supplied LabVIEW installation. That's either some other 3rd party driver, seemingly for a camera, or it could be utility code related to such a device that was added by someone else in the organization earlier in that project's life.
I guess you might still try copying atmcd32d.llb (and all other seemingly camera-related files) to the path LabVIEW expects to find it (under LV 2018 as seen in your msg #5 screencap). But I'm less confident it'll work than I was the first time I suggested it.
-Kevin P
CAUTION! New LabVIEW adopters -- it's too late for me, but you *can* save yourself. The new subscription policy for LabVIEW puts NI's hand in your wallet for the rest of your working life. Are you sure you're *that* dedicated to LabVIEW? (Summary of my reasons in this post, part of a voluminous thread of mostly complaints starting here).
