Subject | Re: [IBO] result fields concatenated null |
---|---|
Author | Daniel Rail |
Post date | 2002-04-27T22:34:46Z |
At 04/27/2002 05:53 PM, you wrote:
standard. I use a stored procedure to concatenate fields, when I know that
they are the same fields all the time.
If you don't want to use stored procedures, then I would suggest that you
use calculated fields to concatenate the strings. The calculated fields
are handled by the application, by the event OnCalcFields.
These are two solutions that can be used.
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.accramed.ca)
>I.NOME||'. '||TC.DESCRICAO||'. '||C.DESCRICAO AS CONTAThis is a normal behavior for Interbase or Firebird as per SQL-92
>
>When the field C.DESCRICAO is Null, my result CONTA is null to.
>Anyone can help-me? If any field of this concatenation will null, I don't
>want that the result was null.
standard. I use a stored procedure to concatenate fields, when I know that
they are the same fields all the time.
If you don't want to use stored procedures, then I would suggest that you
use calculated fields to concatenate the strings. The calculated fields
are handled by the application, by the event OnCalcFields.
These are two solutions that can be used.
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.accramed.ca)