Subject | Re: Group by problem... |
---|---|
Author | johanfredse |
Post date | 2003-05-27T08:37:18Z |
Hello Set,
Well...the ALARM_GRP holds a value 0 to 5 defining different
alarmgroups. I was grouping the now not working way in the previous
database that was DBISAM.
Normally they are not changed in between history savings but now and
then it is and will then mess up the display routines. So I can skip
it completely or use as You said, a MAX(..) for it.
Hmm...I use MAX(...) for know and dig into SP later on.
Cheers
/Johan
Can't help being a Swede...buhuuu... ;-) Can convert to Norwegian...
--- In ib-support@yahoogroups.com, Svein Erling Tysvaer
<svein.erling.tysvaer@k...> wrote:
Well...the ALARM_GRP holds a value 0 to 5 defining different
alarmgroups. I was grouping the now not working way in the previous
database that was DBISAM.
Normally they are not changed in between history savings but now and
then it is and will then mess up the display routines. So I can skip
it completely or use as You said, a MAX(..) for it.
Hmm...I use MAX(...) for know and dig into SP later on.
Cheers
/Johan
Can't help being a Swede...buhuuu... ;-) Can convert to Norwegian...
--- In ib-support@yahoogroups.com, Svein Erling Tysvaer
<svein.erling.tysvaer@k...> wrote:
> Johan,values
> you desire something that doesn't make sense. If some rows contain
> ALARM_GRP = 'Yes' and others ALARM_GRP = 'No', then which of these
> should be returned if you don't want them included in the groupby? If it
> is irrelevant, then you could turn that field into an aggregatefield -
> e.g. by using MAX(ALARM_GRP).
>
> Set
> -oops, I think I just tried to help a Swede...