I am not saying that you cannot use CWGraph with DAQmx, and I agree that it would be ridiculous for the CW user interface controls to somehow have a dependency on a particular driver. You can use any of the Measurement Studio ActiveX user interface or analysis controls with any hardware library (including 3rd party hardware libraries).
The issue at hand is that the implementation of the DAQ ActiveX controls is tied directly to the driver itself. The CWAI, CWAO, etc. controls were developed on top of the Traditional DAQ driver. They were created years before the DAQmx driver existed.
The DAQmx driver API is radically different than the Traditional DAQ driver, not only in its public API, but also throughout the entire software stack. The API incompatibility that prevents the ActiveX controls from working with the DAQmx driver applies to the ANSI C interface as well as the ActiveX interface. Unfortunately, when we moved to DAQmx, all of our customers had to change the way they programmed their DAQ devices. We weren't happy about introducing this incompatibility, but there was no reasonable way to keep the API consistent and correct all of the functional inadequacies in the Traditional DAQ driver.
I would also like to clear up what seems like a packaging misunderstanding. The CW DAQ controls (CWAI, CWAO, etc.) are included free with the Traditional DAQ driver. You do not need to purchase Measurement Studio to use these controls.
We would like to help you be successful with Measurement Studio in VB6, regardless of which driver you use. Please let us know if you have additional concerns or questions as you get started with your application.
