HI,
First - sorry, never sure whether to put these type posts in users, dev
or qa.
I entered Issue 87054 today - in a nutshell what it is regarding is the
use of groups NOT based on actual fields in the result set a report
builder report is based on. This was something you could do with SRB
1.0.x by adding a static string into the group by dialog box.
Under SRB 1.0.2 this causes an error in the generated SQL statement as
it adds an order by clause to the select statement using this string.
Bummer.
However, I now see that I can indeed still do this - but what must now
happen is that the group must be based on an empty string. In other
words open the group/sort dialog, go to the an add group line - drop
down the list of columns and close it again without selecting any
column. This adds the group and the group header by default and we can
get the behavior that was available under 1.0.1.
One catch, if I am not mistaken there is an issue for this specific
action as a defect - this adding the group when no column was selected
in the drop down ( IIRCC ).
So -given all this would it be correct to go back and mark Issue 87054
as invalid, or works for me, since the actual feature is available only
in a more restrictive way - and - if that is the case, then should I go
looking for that other issue about the drop down list causing a group
when no column is selected and marking entering a comment that it should
be retained as a 'feature'?
Thanks
Drew
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
