Help: LabVIEW Application Builder Chumps it on Daq.dll

[Peter de B. Harrington]

We are building a LabView application with the application builder and are
using all the most current versions. The application either processes data
off a DAQ card or a file, but when we install the application on a system
without LabVIEW, the VI has broken links and the install reports several
dlls are missing. The first one is nidaq32.dll.

Does this mean that we must bundle all the dlls used in the application? I
would think that the applicatoin builder would include them in the run time
library as a default.

Is there an easy way to bundle the Nidaq dll's in the install as a default
so that they load if no other dll's are present?

Or is there away to configure the VI, so that it does not depend on these
VI'
s when it is installed on a machine without a DaqCard?

TIA,

Pete

[shoneill]

You need to have NI-DAQ installed on the target computer to allow the program to run.

I think you can use LabVIEW`s VI-Server capabilities to allow for dynamic loading of VIs which do or do not rely on NI-DAQ, depending on the environment. If the NI-DAQ functions are "hard-wired" into your diagramm, these errors will occur. How to check for NI-DAQ Install without using a NI-DAQ VI I don`t know....

Shane

[Peter de B. Harrington]

Thanks,

Pete

"shoneill" wrote in message
news:5065000000050000008ECB0000-1042324653000@exchange.ni.com...
> You need to have NI-DAQ installed on the target computer to allow the
> program to run.
>
> I think you can use LabVIEW`s VI-Server capabilities to allow for
> dynamic loading of VIs which do or do not rely on NI-DAQ, depending on
> the environment. If the NI-DAQ functions are "hard-wired" into your
> diagramm, these errors will occur. How to check for NI-DAQ Install
> without using a NI-DAQ VI I don`t know....
>
> Shane