01-28-2009 11:08 AM
06-04-2009 11:15 AM
I am having the exact same issue on a customer's computer. Has a solution been found?
Brian
06-05-2009 11:52 AM
Hi Brian,
We have determined that this is indeed a bug, and have filed CAR ID 142961. It will likely be fixed in an upcoming version of DAQmx, I would check the readme file for the next version to see if a fix is available. Just look for the CAR ID in the Fixed Issues section.
In the meantime I am not aware of a workaround other than reverting to a previous version of DAQmx.
-John
06-12-2009 05:10 PM
Hi Brian,
I apologize, I had misread the bug that R&D had reproduced and fixed--please disregard my previous post.
We have gone through great lengths to try to reproduce the behavior that you are experiencing and have still been unable to do so. If you have any specific instructions for us we can continue to try to recreate the problem--this would be the first step in looking into a possible fix.
-John