Alexandre, thanks for the reply.
I just changed the sql to use alias for the table names to convince the IBO
parser, that the SQL is editable.
But it still thinks it cannot be edited.
Well, the query-sql indeed is not editable, but the insert-sql is. And the
parser doesn't seem to look at it (update sql looks similar):
INSERT INTO EINKAUFHISTORIE(
REF, /*PK*/
DATUM,
LIEFERANTENNR,
KURZNAME,
TEXT,
EFFEKPREIS,
EKPREIS,
AUFSCHLAG,
FRACHTKOSTEN,
SONSTKOSTEN,
RUNDUNG,
VKPREIS,
ARTPREISBERECHNUNG,
EINKAUFMENGE,
DATUMPREISAEND,
REF0)
VALUES (
:REF,
:DATUM,
:LIEFERANTENNR,
:KURZNAME,
:TEXT,
:EFFEKPREIS,
:EKPREIS,
:AUFSCHLAG,
:FRACHTKOSTEN,
:SONSTKOSTEN,
:RUNDUNG,
:VKPREIS,
:ARTPREISBERECHNUNG,
:EINKAUFMENGE,
:DATUMPREISAEND,
:REF0)

Regards
Gunther


Am 15 May 2008 um 4:19 hat amoradell geschrieben:

> Hello,
>
> It's good practice to use an alias for tablename
> when you use several tables or same table many times, so you could add
> on your query :
>
> FROM EINKAUFHISTORIE E
>
> select min(e1.effekpreis) as MINI,max(e1.effekpreis) as MAXI,
> min(e1.ref0) as
> ref0temp from einkaufhistorie e1
> where e1.ref0=:MLNK_REF0_0 and e1.effekpreis>0
> and F_ADDDAY(e1.datum,<<MINMAXTAGE>>)>='now'
>
> on mm.ref0temp=e.ref0
>
> I dont know how IBOjects handle this without table alias but I suspect
> that it couldnt guess the editable status of EINKAUFHISTORIE.
>
> Regards
>
> Alexandre
>
> PS : I think also Fb 20 is less tolerant on that (see Release notes)