Subject | Re: Columnattributes T_YESNO=BOOLEAN=1,0 doesn't work if SQL contains "group by" |
---|---|
Author | clivewalden |
Post date | 2006-11-02T17:32:34Z |
First questions:
1. Why is the same field defined in some places as TBooleanField and
others as TSmallIntField? That might help with the "best" solution.
2. How is the POSTED column actually defined in the database and what
constraints are in place?
Clive
1. Why is the same field defined in some places as TBooleanField and
others as TSmallIntField? That might help with the "best" solution.
2. How is the POSTED column actually defined in the database and what
constraints are in place?
Clive
--- In IBObjects@yahoogroups.com, "Frederic Bell" <freddie@...> wrote:
>
> Columnattributes T_YESNO=BOOLEAN=1,0 doesn't work if SQL contains
> "group by", however it DOES WORK of the SQL doesn't contain "group by"
>
> I am converting an extensive BDE application (not written by me).
>
> SQL.TEXT := 'Select account, posted, amount from DTRANS"
> ACCOUNT: TStringField
> POSTED: TBooleanField
> Amount: TBCDField
>
> if (Posted) then // compiles fine
>
> SQL.TEXT := 'Select account, posted, Sum(amount) from DTRANS"
> ACCOUNT: TStringField
> POSTED: TSmallIntField
> Amount: TBCDField
>
> if (posted) then // NOW needs to be changed to: if (posted = 1)
>
> The most recent grep indicates that the app contains over 400
> 'occurances of the "group by" clause along with sundry associated .pas
> code. That's a lot to check and fix manually! Any assistance/comments
> appreciated. Thanks.
>