Hi,

At April 22, 2003, 21:16, Helen Borrie wrote:

> At 04:40 PM 22/04/2003 -0300, you wrote:


>> > What about the OrderingItems - how are they defined?
>>
>>I know what you're thinking, I've encountered the same problem before
>>when using display labels in the Ordering Items. Thanks for reminding
>>me that I forgot something in my message. Any ideas are welcomed.
>>
>>Ordering Items:
>>PG1_FIRSTNAME=PG1_FIRSTNAME;PG1_FIRSTNAME DESC
>>PG1_LASTNAME=PG1_LASTNAME;PG1_LASTNAME DESC
>>PG1_HOME_PHONE=PG1_HOME_PHONE;PG1_HOME_PHONE DESC
>>PG2_FIRSTNAME=PG2_FIRSTNAME;PG2_FIRSTNAME DESC
>>PG2_LASTNAME=PG2_LASTNAME;PG2_LASTNAME DESC
>>PG2_HOME_PHONE=PG2_HOME_PHONE;PG2_HOME_PHONE DESC
>>FAMILY_ID=FAMILY_ID;FAMILY_ID DESC
>>
>>Ordering Links:
>>PG1_FIRSTNAME=ITEM=1;POS=0
>>PG1_LASTNAME=ITEM=2;POS=0
>>PG1_HOME_PHONE=ITEM=3;POS=0
>>PG2_FIRSTNAME=ITEM=4;POS=0
>>PG2_LASTNAME=ITEM=5;POS=0
>>PG2_HOME_PHONE=ITEM=6;POS=0
>>FAMILY_ID=ITEM=7;POS=0
>>
>>Search Links:
>>PG1_FIRSTNAME=PG1_FIRSTNAME
>>PG1_LASTNAME=PG1_LASTNAME
>>PG1_HOME_PHONE=PG1_HOME_PHONE
>>PG2_FIRSTNAME=PG2_FIRSTNAME
>>PG2_LASTNAME=PG2_LASTNAME
>>PG2_HOME_PHONE=PG2_HOME_PHONE
>>FAMILY_ID=FAMILY_ID

> Daniel,
> What release version of IBO are you using?

It's IBO 4.2Id.

> It looks to me as if the parser might be blindly seeking out the string
> 'FIRST' and breaking up the pieces in some arcane way...so you are getting
> this weird behaviour, where the identifiers for the database column
> FIRSTNAME in the SQL are getting mangled to

> SELECT First NAME PARENTS.FAMILY_ID
> FROM PARENTS
> WHERE PARENTS.FAMILY_ID=?

> What's the actual SQL of the dataset? I'm guessing here that
> PG1_FIRSTNAME, PG2_FIRSTNAME, etc. are output columns for a re-entrant
> query, not database columns...right?

Actually they are actual column names. Here's the DDL for the table:

CREATE TABLE PARENTS (
FAMILY_ID INTEGER NOT NULL,
PG1_FIRSTNAME FIRSTNAME collate WIN1251,
PG1_LASTNAME LASTNAME collate WIN1251,
PG1_ADDRESS ADDRESS collate WIN1251,
PG1_CITY CITY collate WIN1251,
PG1_POSTAL_CODE POSTAL_CODE collate WIN1251,
PG1_HOME_PHONE HOME_PHONE collate WIN1251,
PG1_OTHER_PHONE HOME_PHONE collate WIN1251,
PG1_EMAIL EMAIL collate WIN1251,
PG1_VOLUNTEER_NO INTEGER,
PG2_FIRSTNAME FIRSTNAME collate WIN1251,
PG2_LASTNAME LASTNAME collate WIN1251,
PG2_ADDRESS ADDRESS collate WIN1251,
PG2_CITY CITY collate WIN1251,
PG2_POSTAL_CODE POSTAL_CODE collate WIN1251,
PG2_HOME_PHONE HOME_PHONE collate WIN1251,
PG2_OTHER_PHONE HOME_PHONE collate WIN1251,
PG2_EMAIL EMAIL collate WIN1251,
PG2_VOLUNTEER_NO INTEGER);

/* Primary keys definition */
ALTER TABLE PARENTS ADD CONSTRAINT PK_PARENTS PRIMARY KEY (FAMILY_ID);

/* Indices definition */
CREATE INDEX PARENTS_IDX ON PARENTS (PG1_LASTNAME, PG1_FIRSTNAME);
CREATE INDEX PARENTS_LF_NAME ON PARENTS (PG1_LASTNAME, PG1_FIRSTNAME);
CREATE INDEX PARENTS_PG1_CITY ON PARENTS (PG1_CITY);
CREATE INDEX PARENTS_PG2_CITY ON PARENTS (PG2_CITY);

Your interpretation of the probable cause is pretty much of what I was
starting to think.

--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)