No problem was not in the tool itself. I changed
If(exist) to a new statement

select 1 from RDB$Database
Where ...
Into :numrows;
If (numrows is not null) then
exception;

and then everything was OK. It seem that problem was related to
IF (exists) command.

Rade

--- In firebird-support@yahoogroups.com, "Martijn Tonies"
<m.tonies@u...> wrote:

>
> > I found a new problem.
> >
> > This procedure work fine every time only if i run it through
> > debugging process. When i run it through IB_console it does not
> > generate an exception but if i use IBExpert and start debugging

on

> > it it does. What could go wrong with a procedure definition.
>
> Well, you haven't shown us the full procedure.
>
> Either way, this sounds like a bug in the IBExpert procedure
> debugger.
>
> With regards,
>
> Martijn Tonies
> Database Workbench - developer tool for InterBase, Firebird, MySQL

& MS SQL

> Server
> Upscene Productions
> http://www.upscene.com
>
> > --- In firebird-support@yahoogroups.com, "radevojvodic"

<vrade@i...>

> > wrote:
> > >
> > > Hi All,
> > >
> > > I have a stored procedure which is called from application with
> > > IBobjets' TIB_StoredProc. The problem is that i have an select
> > > statement which should generate an exception. Calling a stored
> > > procedure from IB_console works OK and it produces an

exception,

> > but
> > > if I call the same procedure from my application an exception

is

> > not
> > > generated and stored procedure executes normaly (and it should
> > not).
> > > Does anyone know the reason. Is there a known problem with

select

> > > statement and exists clause
> > >
> > > e.g.
> > >
> > > if( exists(
> > > Select 1 From RDB$DATABASE\
> > > Where exists(Select...)
> > > ) then
> > > Exception E....
> > >
> > > RADE