AndrewMc
2006-12-15 17:40:11 UTC
Hey Matt,
Another thing that you could do in your application that might help is this:
If you are not needing DAQmx in every instance of the application, you could only load the DAQmx driver if the functionality is required. To do this, you could isolate all DAQmx calls into a separate DLL. Then you can load that DLL at runtime (via late-binding in VB) only if DAQmx is installed on the system (If it's not, you could install it at that point). This way, you won't always need DAQmx to be installed on the computer, and you can load it only when the DAQ card is required.
By the way, in my previous post a referenced a method to check a file existence to see if DAQmx is installed. A good file to reference is nicaiu.dll, which is always located in the system32 folder. If that file is not present, DAQmx is not installed.
Another thing that you could do in your application that might help is this:
If you are not needing DAQmx in every instance of the application, you could only load the DAQmx driver if the functionality is required. To do this, you could isolate all DAQmx calls into a separate DLL. Then you can load that DLL at runtime (via late-binding in VB) only if DAQmx is installed on the system (If it's not, you could install it at that point). This way, you won't always need DAQmx to be installed on the computer, and you can load it only when the DAQ card is required.
By the way, in my previous post a referenced a method to check a file existence to see if DAQmx is installed. A good file to reference is nicaiu.dll, which is always located in the system32 folder. If that file is not present, DAQmx is not installed.