We had a similar problem with another company's DAQ hardware. It turns out they put their DAQ VIs in VI.Lib, but in their own folder, and something didn't get picked up when the Build was made.
It turns out that there were Text files with who-knows-what (probably configuration data) that were stored in a folder "data" within the Vendor's folder inside VI.lib. When you do a Build, a data folder is created along-side the Executable. Copying the text files from the Vendor's "data" folder to the Build's data folder fixed this problem, but what a kludge!
Bob Schor
