Hello aplication_dev…,
We have completed the investigation. It looks like the crash was caused by a user error in function Bind_Money. In that function a local variable is being bound to the library. After the function executes, the variable stops existing, but its address is saved by the library.
When calling DBFetchNext, the library tries to write the status of the request at the specified address. But the variable stat does not exist anymore. And, because it was a local variable, it was allocated on the stack. Thus, the library tries to modify a value on the stack that exists no more and this leads to the corruption of the stack and the crash.
The fact it doesn't crash in debug mode and with older versions appears to be coincidental.
The help for the binding functions states that the status parameter is a "pointer to the variable that receives the status value of the specified column when you fetch a record." It might not be that obvious that it has the same importance like the address that is being bound to the column, so we are going to modify the documentation to provide this information. Also, please note that you can't pass a NULL value to the binding function. I would suggest adding the status variable to the CURRENCY structure and use it to determine if the information returned was NULL or if it was truncated.
Please let us know if you encounter any other issues.
Best regards,
= Nelu F. || National Instruments.
