Subject | Re: Bug in 3.6A IBOQuery |
---|---|
Author | paulhope@allcomm.co.uk |
Post date | 2000-12-06T21:39:53Z |
Jason
value (an encrypted '0') and it would just be too tedious!
I have got round it by using an TIB_Query but thought it was worth
raising.
Regards
Paul
> I'll log this as a potential bug. I'm sure you can work around itby using
> two separate parameters, right?Wrong! The real query has about 20 fields initiated with the same
value (an encrypted '0') and it would just be too tedious!
I have got round it by using an TIB_Query but thought it was worth
raising.
Regards
Paul
> > Hiand a
> >
> > There appears to be a bug in TIBOQuery when used for Insert SQL
> > parameter is repeated.
> >
> > Create table test(f1 varchar(15),f2 varchar(15))
> >
> > SQL is set to
> >
> > 'insert into test values(:p1,:p1)'
> >
> > query is connected to autocommit transaction.
> >
> > code is
> >
> > Query.ParamByName('p1').AsString:='test';
> > Query.execSQL;
> >
> > result is
> >
> > both fields are null.
> >
> > Works OK with IB_Query.
> >
> > Regards
> > Paul
> >