LabVIEW
Labview 2018 exe asks for missing vi
Solved!
@vaibhavsl wrote:
Respected All
As per the new discovery. If I make individual .exe of a VI i want to run, it works fine. Only if I call the VI (like login window then at button event required VI opens) then only I got this error.
Below is the program I've attached.
(version used Labview 2018)
Please help me out.
That's logical. When you build an executable, the LabVIEW application builder will collect all dependencies and add them to your executable file. If you just try to call a vi from your executable all the dependencies of that VI are not usually present in your executable. But the VI references those dependencies in a pseudo relative way, namely as being located in vi.lib respective to your current process. Except that your build executable is not located at C:\Program Files (x86)\National Instruments\LabVIEW 20xx but at some other location and hence can't find C:\Program Files (x86)\National Instruments\LabVIEW 20xx\vi.lib but will instead try to find <your executable directory>\vi.lib.
Why do you want to try to call the VI directly and not include it in your executable build?
Yes, why can't you include it all in one build?
On a side note, I strongly recommend to do a few basic tutorials about dataflow. Your code is extremely poorly written and violates all guidelines.
(looking at operator.vi) Basically you have all disconnected controls and operate on data exclusively via value property nodes, To "fix" the resulting race conditions, you corral every "line" into a sequence frame. Two wrongs don't make a right!
Value properties force a thread switch and execute synchronously. Extremely inefficient! A diagram that covers 40x 1080p screens is not maintainable!)
