Hi all,
The only hint, the manuals gabe me on this error is, that
the InterbaseNumber for this error is 335544358L
Now, what can I do to avoid this? ( it doesn't comes up
in the debugging environment, only in the final, running

Robert Beicht wrote:
  (snip)

A little bit of information usually helps. Then we don't have to guess quite as
  much. Tell us about the app, the server, the version of IB, the point in the app
  where the error rises etc.
  Paul

Paul Reeves wrote:
  (snip)

It is IB 5.6, we are accessing it through ODBC API using Dephli (no BDE
  or ADO or anything like this, only a thin-client-odbc-api-interface, we have
  developped). The database is quite a large one, with ~ 300 stored
  procedures, most of them are 'select procedures', used like views (I love

Robert Beicht wrote:
  (snip)

My poor memory recollects this problem is related to using the wrong API call to
  execute a stored procedure. At least, I had this problem when using
  isc_dsql_execute. On checking the code for FIB it transpired that Greg was using
  isc_dsql_execute2 for all SPs. After I made the change, no problem.

I found the solution for this error:
  It was a wrong calling signature for a 'select procedure' (a
  procedure returning something): I have a procedure wich 'does
  something' and returns a state message of what had happened.
  But instead of calling it 'select STATE from MYPROC', I called it

Thanks for sharing it, it must be kept for future reference.
    Probably I never saw it because I stopped using ODBC->IB some time ago and
    never intented to call a selectable sp with execute in an ODBC connection.
    C.
    Robert Beicht wrote in message <✉sulzer.de>...