I have noticed that replacing a. with the actual table name ie animal, and s
with animalactivesire, still results in errors at design time, when you
double click on IB_query, end activate the query, but is parsed correctly at
runtime, thus not giving errors at runtime anymore.



When using the Animal A, Animalactivesire s : causes errors at runtime and
designtime.



I'm sure there must be an error that creaped in with IBO code between FB1.53
and FB2.



I'm currently using IBObjects 4.6.Bc if only I knew where to start looking
in the source code.

It appears he is substituting the short form with the actual table name when
creating the query in SQL.



Regards

Adrian



_____

From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com] On Behalf
Of Adrian Wreyford
Sent: 16 September 2006 02:07 PM
To: IBObjects@yahoogroups.com
Subject: [IBO] Join links causing problems in FB2, not FB1.53



I have old code with that works just fine in FB1.53

IB_Query:

SELECT A.ANIMALIDENTIFICATION, A.ANIMALNAME, A.ANIMALREGISTRATIONNUMBER,

A.ANIMALHERDSTATUS, A.ANIMALDOB, A.ANIMALGENDER, A.ANIMALTAGCOLOUR,

A.ANIMALID, S.ANIMALFIRSTSIREDATE, S.ANIMALSIRESTATUS

FROM ANIMAL A, ANIMALACTIVESIRES S

where A.ANIMALGENDER = 'M'

KeyLinks pane:

ANIMAL.ANIMALIDENTIFICATION=NAT.NATSIREIDENTIFICATION

JoinLinks Pane:

ANIMAL.ANIMALID = ANIMALACTIVESIRES.ANIMALSIREID

Used to work perfectly in FB1.53

Since migration for FB2

Get Error: 335544569

ISC MESSAGE: Dynamic SQL Error SQL error code = -206 Column unkown
ANIMAL.ANIMALID At line 6,column14.

**************************************

If I then change join links pane to:

A.ANIMALID = S.ANIMALSIREID

And change Keylinks pane to:

KeyLinks pane:

A.ANIMALIDENTIFICATION=NAT.NATSIREIDENTIFICATION

I then get error:

FiledName: Animalactivesires.animalfisrtsiredate not found.

This field definitely exists!!

Previously using Animal. instead of A. was acceptable in the Joinlinks etc,
but now appears not to work with other queries of mine aswell.

These are all IB_Queries.

Has something changed.

What must I do now.

When I check my other queries no hassles.

It only appears to pop up these errors when using JOIN LINKS!!

Was 1.53 more leniant towards possible poor coding practices, and if so,
please point out my poor coding practice, I will appreciate this.

I checked Helens book, and could not come up with any issues.

Any help will be appreciated.

Regards

Adrian

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]