Flavio,

At 07:02 AM 7/06/2007, you wrote:

>Good morning Jason
>
>There are days behind solicited one copies of their components in the
>modality Trustware and didn't receive no your answer

If you have a Trustware request, you may write to me, respond@....

>I am converting with the version that have (this Already almost ready)
>put I noticed a problem that reading releases was going detected like
>mistake and already corrected that is the following:
>
>in select with a double key the system didn't find the former field:
>
>select
> (descricao || codigo) the key
>from
> products
>
>the key field wasn't identified by the systems.

This is not a fault of IBO. It is the way SQL works.

The expression

(descricao || codigo) the_key

produces a derived field ("expression field", calculate field) that
is dissociated from the underlying fields in your Products table.

If the expression produces unique values, you can make this derived
field a key for your dataset by using the_key as your
Keylinks. However, if you want the set to be a "live dataset"
(updatable) you should include the actual columns in your SQL:

select
codigo,
descricao,
descricao || codigo the_key
from
products

In that case, you would set codigo as your Keylinks.

Helen