lvStorage.dll and Built application

[Joe_Gerhardstein]

Am running LV 8.0.1, and am created a TDM output file with some measurement results, then sending it to DIAdem using the LV-DIAdem Connectivity VIs.  I built the application and created an installer.  The install goes fine, but when I try to launch the .exe, the the application searches for "lvStorage.dll", which is an NI dll.  I have verified that the .dll is in the data folder that is created by the installer.

Any thoughts?  My workaround at this point is to install a second copy of the DLL in the Windows directory, which is not the best solution, but seems to get the job done.


Joe

[tbob]

I have the same problem with exe's.  The two choices I use are to store a copy of the dll into the same directory as the exe and to store a copy in the Windows\System32 directory.  Not very elegent since I don't like having copies of a dll in more than one place, but it works fine.  One thing I haven't tried yet is to changed the search path in labview so that the original path of the dll is amongst the search list.  But I don't think search paths carry over to exe's.  I wish the dll could be merged into the exe altogether.

The whole idea of the dll needs to be scrapped.  It was invented with the intention that the dll code could be reused to save hard drive space.  But it seems that every program has its own dll, and now there are millions of dll's all over the place.  I would rather the dll code just be imbedded into the exe.

[Joe_Gerhardstein]

If I had to make a guess as to the problem, it would appear that NI's Storage VI's use a DLL that is linked with an absolute path instead of a relative path, but since you can't get into the VIs, there isn't any way to tell for sure.