call library path

[kerek123]

Hi all,

I have a question regarding calling dlls.

Usually when I call a dll I have to write the hole path of it inside the dll properties. However in the drivers on my data acqusition card I have found that the path of the dll is incomplete and only shows the name of the dll (as shown in the picture  attached). I have no idea where that dll is since it doesn't show the path and I have looked for in in windows and I can't find it.

I would like to know why the call library vi doesn't need the path in some cases and if possible any recomendation to find it.

thanks

Juanlu

[TiTou]

---

@kerek123 wrote:

I would like to know why the call library vi doesn't need the path in some cases and if possible any recomendation to find it.

---

It doesn't need the full path because the dll is registered in Windows (Windows knows where the dlls is).

I remember reading a very interesting discussion on the forums about the performance difference you'd get if you specify the full path in the CLFN properties or just the dll name or if you pass the dll path to the CLFN as an input on the diagram.

I can't find this discussion now, maybe someone kept the link 

(CLFN : Call Library Function Node)

[TiTou]

Found it : http://forums.ni.com/t5/LabVIEW/Dr-Damien-s-Development-Call-Library-Function-Node-Calling/td-p/1117...

[rolfk]

Basically LabVIEW will check on load of the VI if the library path is an absolute path or not. If it is, it attempts to load the library from that path. If it is only a file name or the load from the absolute path fails, it instructs Windows to find the DLL, with the name only. If that also fails you get a broken arrow and the failure that the DLL could not be loaded or found.