A user of our VXI product has just ran in to a problem using our plug and play driver and an IVI driver.
His CVI project began getting errors from one of our functions after loading the IVI driver and calling the init function of the IVI driver. If the user omits the init call, the application runs without errors.
Our function that is returning the error is getting the error from "DDAO35.DLL" which is a Microsoft Data Access Objects class library.
From a problem we discovered when testing with TestStand, we know that the DAO library is not multi thread safe and the error returned is similar to what we are seeing now.
How is using an IVI init function call causing this error and is there a workaround.
