I agree with crossrulz and RavensFan--the producer/consumer loop is a great way to control flow of data and prevent accumulation of data in memory. It's also a handy tool to prevent data loss--if you had two loops, one for measuring and one for saving data, but did not have the saving loop dependent on the measuring loop (the dependency that queues create), then you might have problems with racing and either lose data if the saving loop runs too slow, or repeated data if it runs too fast, in comparison to the measuring loop. And using DAQmx level vi's, rather than the DAQ assistant, are definitely a great way to go if you're going to be measuring a lot of data fast and want a very efficient program.
