SELECT routing.customsgroup, routing.waybill,
waybill.surchargeflag1, waybill.surchargeflag2,
waybill.surchargeflag3, waybill.surchargeflag4,
waybill.waydate,
waybill.service, waybill.origpers, waybill.origperadd1,
waybill.origperadd2, waybill.origperadd3, waybill.origperadd4,
waybill.destpers, waybill.destperadd1, waybill.destperadd2,
waybill.destperadd3, waybill.destperadd4, waybill.destperphone,
waybill.destpercontact, waybill.customsvalue,
waybill.currency,
waybill.pieces, waybill.actkg, waybill.chargemass,
waybill.specinstruction,
waybill.subtotal, place.town, contents.description

FROM waybill
INNER JOIN routing on (waybill.waybill = routing.waybill)
LEFT OUTER JOIN place ON (waybill.destplace = place.place)
LEFT OUTER JOIN contents ON (waybill.waybill =
contents.waybill)

WHERE routing.manifest =0
and routing.mbranch =0
and routing.mtype ='M'
and contents.item = 1

ORDER BY routing.customsgroup,routing.sortorder,routing.waybill

Where you see 0 - this is where input parameters are in the app -
just like this for IB console ( using IB6.0 )

--- In ib-support@y..., Svein Erling Tysvaer
<svein.erling.tysvaer@k...> wrote:

> At 07:44 02.10.2002 +0000, you wrote:
> >So my question is - can GDB size effect the plan ? ( GDB 2 780mb

GDB

> >1 180mb - the relations on the query will have a similar size

ratio )

>
> I don't know, I would guess it was rather the data than the size

that

> mattered. But the reason I am answering is because some kind of

tweaking

> your SQL could possibly eliminate your problem. But I couldn't find

a way

> just from your plan - show us your SQL.
>
> Set