LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Reference vi not found although the vi exists.

I opened a LV project from version 2018 with the LabView 2025 (Q1). Although the function list of LV shows the DataFinder library, the old vi's does not load the used DataFinder vi's at all. What I see is only an empty grey box. Of course I could manually exchange those missing vi's but there are so many it is kind of impossible.

 

I tried to add the vi search path directly to the path of the DataFinder library but no success. I also masscompiled my old project but also no success. Here is an example of such corrupted vi:

 

DataFinder TK.png

 

The added search path:

 

search.png

 

The LabView 2018 I do not have installed but I think there must be another workaround.

 

Thanks in advance

0 Kudos
Message 1 of 6
(282 Views)

Have you tried mass compiling the code? You could also search for the VI by right clicking and replacing the one that are not found.

Tim
GHSP
0 Kudos
Message 2 of 6
(266 Views)

You set the include folder to LV 2022, is that intended? DataFinder was moved to the LVAddons folder (C:\Program Files\NI\LVAddons), which automatically shadows the LabVIEW install folder. Perhaps there is an issue with that.

See here about LVAddons: https://labviewwiki.org/wiki/LVAddons

 

0 Kudos
Message 3 of 6
(252 Views)

Why did you add a "2022" search path for LabVIEW 2025? (Also is your 2025 32bit or 64bit?)

 

altenbach_0-1746200061813.png

 

I don't think modifying the search path should be necessary, so something else might be wrong.

0 Kudos
Message 4 of 6
(246 Views)

I am using LV 2025 64bit. I added this additional search path only to see if LV finds the missing vi's - but no success. So I removed it again...

It is correct that I have a DataFinder folder in this path:

 

C:\Program Files\NI\LVAddons\dfc\1\vi.lib

 

So in this case I assume LV should find the missing libs but it does not. I could with right click exchange every missing vi but this would take hours to finish it. So there must be another solution for the issue. 

 

Any other ideas?

 

 

0 Kudos
Message 5 of 6
(172 Views)

Currently I am using LV 2025 64bit the project I am using was made back in 2018 but very likely with LV 32bit. Could this be an issue? If yes, how can I solve it?

 

I have seen the datafinder toolkit is only availabe for 2018 as 32bit.

0 Kudos
Message 6 of 6
(157 Views)