Measurement Studio for VB6

cancel
Showing results for 
Search instead for 
Did you mean: 

Run-time error '48': File not found: nidaq32.dll

Hi, how's it going. When I compile my program, it turns out great on my computer. Works fine. When I transfer the .exe to other computers, it doens't work when the user trys to use it, popping up the message:

Run-time error '48':
File not found: nidaq32.dll

i have nidaq32.dll on my computer in my windows/system folder... please tell me what i should do to get the program to work on other computers as well.
0 Kudos
Message 1 of 5
(5,819 Views)
Salsa,

You will need to install NI-DAQ on the other computer for your application to work. You can find NI-DAQ driver in the Measurement Studio CD in \Redist\NIInstallers\Daq**

For more details you may want to look up Distributing and Installing Measurement Studio Applications help topic in Visual Basic Help->Tutorials found in the Measurement Studio Reference.

A/G
Abhishek Ghuwalewala | Measurement Studio | National Instruments
0 Kudos
Message 2 of 5
(5,819 Views)
So you're telling me that whenever I create a program with the NI-DAQ, and after I compile on Visual Basic, I have to install all the NI-DAQ stuff on the other computers also? That doesn't sound right, I know that is one way to do it, but there should be a way in which once you compile a program, all you have to do is run/install it.

I really don't wanna have to put the NI-DAQ stuff on the other computers, just my program. Does anybody know how to do this...Is this possible, if so please explain. Thanks
0 Kudos
Message 3 of 5
(5,819 Views)
It is true that you must install NI-DAQ on the target machine. NI-DAQ is implemented in a set of DLLs. This means that the code that executes that communicates with the NI-DAQ hardware is inside those DLLs.

The nature of a DLL is that it exists standalone from the executable applications that use it. That means that when you build your executable, the code in the DLL does not get compiled into the executable. Since your program is executing code that resides in the DLL, the DLL must be on every machine that you run your executable on.

One of the purposes of DLLs is to save space on your machine. Another purpose of DLLs is to allow the DLL publishers to fix bugs and update functionality without you having to rebuild the programs that call th
em. This is what typically occurs when you install an operating system service pack.

This scheme is in no way specific to NI-DAQ. In order to run any VB-created application on a machine you must first have the VB run-time DLLs installed on that machine. You might not see this because your target machines probably already have the VB run-time DLLs installed on them for another reason.

See the following URL for more information.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/dll_0qr7.asp

David Rohacek
National Instruments
0 Kudos
Message 4 of 5
(5,819 Views)
I see, that shouldn't be too bad.

Thanks for the help guys.
0 Kudos
Message 5 of 5
(5,819 Views)