I really works now. I am happy, you saved the day!
Best regards,
septimiu

--- lseptimiu@... wrote:

> OK, thank you again. Have a nice day! I guess this
> may
> be the right way for my problem.
> Best regards,
> Septimiu
>
> --- lseptimiu@... wrote:
>
> > thank you for your answer
> > I my procedure looks like this
> > CREATE PROCEDURE S_UPD_SVANIPF (
> > SCOTIZ INTEGER,
> > SAPORT INTEGER,
> > CDA VARCHAR (13) CHARACTER SET NONE,
> > CCA VARCHAR (13) CHARACTER SET NONE,
> > CCC VARCHAR (13) CHARACTER SET NONE,
> > CDC VARCHAR (13) CHARACTER SET NONE,
> > IDPF INTEGER)
> > AS
> > begin
> > //CODE
> >
> > end
> > ok,
> > and the code where i use Ib_StoredProc is:
> >
> > with Sprocedure do
> > begin
> > Sprocedure.StoredProcName:='S_UPD_SVANIPF';
> > try
> >
> >
>

Sprocedure.FieldByName('IDPF').AsInteger:=IntegerVal;

> >
> > Sprocedure.FieldByName('CCC').AsString:=StringVal;
> >
> > Sprocedure.FieldByName('CDC').AsString:=StringVal;
> >
> > Sprocedure.FieldByName('CDA').AsString:=StringVal;
> >
> > Sprocedure.FieldByName('CCA').AsString:=StringVal;
> >
> >
>

Sprocedure.FieldByName('saport').AsInteger:=IntegerVal;

> >
> >
>

Sprocedure.FieldByName('scotiz').AsInteger:=IntegerVal;

> > Sprocedure.Prepare;
> > Sprocedure.ExecProc;
> > finally
> > end;
> >
> > end;
> >
> > So, I still receive that error. "Field IPF is
> > missing".
> > If I move the line where I am setting IPF value, I
> > receive the same error but 4 the next field.
> > I don't know where is the bug.
> > Thank you very much for your answer.
> > --- Helen Borrie <helebor@...> wrote:
> >
> > > At 02:07 AM 19/06/2005 -0700, you wrote:
> > > >can anyone help me by sending a small example
> > using
> > > >Ib_StoredProcedure?. I have some troubles when
> I
> > > try
> > > >to execute a procedure with external
> parameters.
> > I
> > > >receive the following error: "Field IDF not
> > > >found"...where IDF is a variable declared in
> > > >procedure's body.
> > > >Please, help, and excuse me because I am asking
> > > such a
> > > >fullish thing.
> > >
> > > IBO returns database engine errors to the
> client.
> > > If your stored procedure
> > > is returning this error, then it indicates that
> > > there is a run-time error
> > > in your stored procedure code. IBO has no
> > knowledge
> > > of any variables
> > > declared inside a stored procedure; nor,
> indeed,
> > > does it know anything
> > > about the SP except the number, order and data
> > types
> > > of its input and
> > > return arguments.
> > >
> > > IBO will throw this error (or one that seems
> > > similar) itself if you try to
> > > pass values to parameters that do not exist as
> > > params.. IBO parameters
> > > must correspond to the SP's input arguments,
> > > although the names of the
> > > parameters do not have to be the same as the
> names
> > > specified in the SP's
> > > declaration.
> > >
> > > So - you will need to give us more information.
> > For
> > > help with a stored
> > > procedure that returns exceptions at run-time,
> use
> > > the firebird-support list.
> > >
> > > Helen
> > >
> > >
> > >
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam
> > protection around
> > http://mail.yahoo.com
> >
>
>
>
>
> ____________________________________________________
>
> Yahoo! Sports
> Rekindle the Rivalries. Sign up for Fantasy Football
>
> http://football.fantasysports.yahoo.com
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com