I believe the spec that you mentioned is in regards to LabVIEW's interface to a DAQ card through the NI-DAQ driver. This driver is called by LabVIEW to interface to National Instruments boards and will allow you to manage buffer size. With activeX, you are calling methods or reading/writing properties that have been exposed by another program. I assume the data in the 3rd party datalogger is exposed as a property and you are reading this property from LabVIEW via activeX. In this case, the data transfer will be dependent on your system and the 3rd party software. The acquisition rate should be controlled by the datalogger software, but is there a specific processing loop rate you are trying to achieve?