At 05:02 PM 27/07/2006, you wrote:

>Hi,
>
>The question is addressed to Jason and Helen but anyone who knows can
>answer.
>
>I have a stored procedure which returns just one row.
>TIB_StoredProcedure in my app is causing an error SQLDA missing or
>incorrect... I changed StoredProcedure HasForSelect parameter to true
>and the error dissapeared. But in the meantime i changed back from
>4.6.Bc to 4.6.A and i don't know what was the real solution to my
>problem. So, my question is could falsed HasForSelect parameter cause
>this error.

Well, it depends on the stored procedure and how you invoke it...

- If it is a selectable SP, then StoredProcedureForSelect should be
true and it will be valid to call the Open method

- If it is an executable SP, then StoredProcedureForSelect should be
false and it will also return an exception if you try to call Open
(you must call Execute)

Personally, I avoid the stored procedure classes. Too much noise for
me and really rather silly. I think Jason only implemented them for
compatibility with the BDE. I use TIB_Cursor or TIB_Query to call a
selectable SP and I use TIB_DSQL to execute an executable one. More
efficient and there's not that snarl-up with the parameters (as in
your case) if you get one thing wrong.

Helen