I'm interfacing with an Oracle 11g database using stored procedures. I can successfully connect & modify values in the database using input parameters. However, any attempt to get values from an output parameter of any type causes the application to hang, not crash, but stop at the DBGetParam___statement. There are no specific examples to cover this issue, but there's a "standard code snipet" that's used to illustrate how to implement procedure calls using parameters. I've implemented this method as shown with no success. There seems to be some method that the output parameter values get assigned after the SQL statement is closed....but the examples don't elaborate how that is done. Also, there's a LabView reference which states the following when trying to do the same operation using the database connectivity toolset >>> You must also reserve memory space for the output parameter before the query is executed. If this is not done, the returned output parameter will likely be truncated or not returned at all.
This is exactly what I'm experiencing & would like a solution if one exists. I'm assuming that the DBSetParam____ does that function/memory allocation.
I'm using LabWindows CVI 2013 SP2 with CVI Toolkit 2.3.