Subject | Re: [IBO] Another parameter example |
---|---|
Author | Jason Wharton |
Post date | 2003-11-07T15:08:54Z |
I've been given the impression that the parameter ordering is going to be a
big pain in the butt still. Apparently the code to emulate the old behavior
doesn't actually emulate the old behavior. People are going to be forced to
get the latest of IBO and use the new straight parameter ordering methods.
Question is, do we consider asking Nicholas to fix the code so it will match
the old way.
Jason Wharton
big pain in the butt still. Apparently the code to emulate the old behavior
doesn't actually emulate the old behavior. People are going to be forced to
get the latest of IBO and use the new straight parameter ordering methods.
Question is, do we consider asking Nicholas to fix the code so it will match
the old way.
Jason Wharton
----- Original Message -----
From: "Paul Hope" <paulhope@...>
To: <IBObjects@yahoogroups.com>
Sent: Wednesday, August 06, 2003 5:16 AM
Subject: Re: [IBO] Another parameter example
> Hi Calin
>
> > > about FCombineDuplicateParams - where do you suggest I change it.
> > If I recall corectly it is true in only one place.
> > Find that place and set it to false.
> >
> > It should be where the statement is created, otherwise is no good.
> >
> I found it in IBA_UpdateSQL line 210 and set it to false. This corrected
> the probelm I was having with DeleteSQL
>
> delete from forecast_accounts where acno=:old_acno
> and company=:old_company
> and not exists(select * from rep_forecast f where f.acno=:old_acno
> and f.company=:old_company)
>
> I also found it in IBA_Statement.imp and set it to false. This did not
cure
> the problem with standard SQL. These are the only 2 units where it is
set.
>
> Thanks for your help anyway
>
> Regards
> Paul