Thanks for the response. This application has been running with Traditional DAQ for a few years now. No changes have been made to the application in regards to the existing traditional daq stuff. New code has been added, but nothing added using traditional daq. The only other thing that has changed is the PC (new PC with latest Intel processor, originally running XP, but since has been reformatted and Win2000 has been loaded).
In direct response to your suggestion, both nidaq32.bas and nidex32.bas are included in my vb6 project. These .bas modules contain the routine declares for access through the nidaq32.dll and nidex32.dll files. The file nidaq32.dll can be located on my target PC (running Windows2000). There are also registry entries when I search for nidaq32.dll in the registry. However, the file nidex32.dll cannot be found on the target PC. This file is definitely not installed with the latest driver installations we use (NIDAQmx 8.3, NISwitch 3.4, NIDMM 2.6). Not sure if that is normal or not. I probably need to check other PCs that are running this same application without problems.
I suspect it's either a PC incompatibility with the traditional daq drivers or it's a driver installation problem. Not sure what else to try at this point other than rewrite my application using NIDAQmx rather than Traditional DAQ. This is a bad short-term option since a rewrite will take significant time.