LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Concerning Stored Procedures in LabVIEW..

Can someone explain to me why LabVIEW cannot receive parameters from stored procedure calls? Is the problem with LabVIEW, the ODBC interface, the Intersolv driver, or Oracle? And does anyone know of any workarounds besides using select statements? Thanks for the help!
0 Kudos
Message 1 of 4
(3,067 Views)
Sal,

I have seen some quirky things with the labview sql toolkit. sql statments that work in Access somtimes won't work when pasted into the sql toolkit. Things that make these problems go away are changing (or adding) single quotes to double quotes, square brackets instead of parentheses, Using the words "PROCEDURE proc_name" (remove quotes, change proc_name to the actual name)in front of the sql statment(s).

I don't have much experience with passing parameters to / from stored procedures so I can't speak exactly about your problem, but maybe something above will help.

Jared
0 Kudos
Message 2 of 4
(3,067 Views)
Have you looked at the example "Using Database Stored Procedures, Transactions, and Exceptions for Oracle 8.0.4."? It can be found at http://zone.ni.com/devzone/devzoneweb.nsf/opendoc?openagent&0B1F619CAC4819F486256879004F84A9&cat=0F9EE47C28AA0628862567AC004EDCE3
0 Kudos
Message 3 of 4
(3,067 Views)
Hi Dennis,
Yes, I've looked at the example. But in the example, they use select statements instead of stored procedures, again because LabVIEW doesn't handle stored procedures correctly. I was trying to find out why aren't they handled correctly.
0 Kudos
Message 4 of 4
(3,067 Views)