Subject Re: [firebird-support] Re: Interbase to Firebird conversion, Delphi
Author Thomas Steinmaurer
>>>> If anyone has done any Interbase to Firebird conversions, here
> is
>> a
>>>> question for you..please help!
>>>>
>>>> I converted from Interbase 6 to Firebird Embedded
>>>> I kept the original ibx components and everything seemed to work
>> fine
>>>> until I got
>>>>
>>>> Dynamic SQL Error
>>>>
>>>> SQL error code = -206
>>>>
>>>> Column unknown
>>>>
>>>> SKAAP.FAMILIE_ID
>>>>
>>>> At line 1, column 86.
>>>>
>>>> I get this on a number of queries and it worked fine on
> Interbase.
>>>> The fields are in the table, I checked the queries too. The
> weird
>>>> thing is that some fields are found and others not. All in the
>> same
>>>> table! No quotes were used.
>>> The most likely thing is that your problem queries are using a
> mix
>> of table identifiers and relation aliases to qualify the column
> names
>> (or some qualified and some not). From Fb 2-forward, this is
>> invalid. Use either all table identifiers or all aliases and don't
>> omit any.
>>> ./heLen
>>>
>> Thanx heLen!
>> I checked quickly, but there aren't any aliases. Could I provide
> the
>> code that I'm using, maybe you see something I don't?
>> :
>
> qgetcards:
> select
> KAART_DETAIL.KAART_DETAIL_ID,
> cardfields.displayname_a,
> cardfields.displayname_e,
> cardfields.displayfield,
> cardfields.tablename,
> cardfields.lookuptable,
> cardfields.lookupfield,
> KAART_DETAIL.CARD_CAPTION,
> cardfields.card_group,
> cardfields.idfield,
> cardfields.idvalue
> FROM
> cardfields,KAART_DETAIL,KAARTE
> WHERE
> ((cardfields.cardfields_id = KAART_DETAIL.CARDLOOKUP_ID)
> AND
> (KAART_DETAIL.KAARTE_ID = KAARTE.KAARTE_ID)
> AND
> (KAARTE.KAARTE_ID = :KAARTE_ID))
> ORDER BY KAART_DETAIL_ID

This query works fine for me in Firebird 2.1 with your metadata provided.

Perhaps IBX is trying to generate additional SQL behind your scene? E.g.
in the TIBDataset component? Is there some kind of monitoring/tracing
component in IBX which allows you to nail down the SQL statement which
really produces the error?




--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com
My blog:
http://blog.upscene.com/thomas/