Dragan,

Thanks for the description. It'll suffice for now.

Alex

>>Kevin. What you have done sounds very interesting. Would you give more details ? I use EVAL(tcGroupBy) which I might have learned from Dragan, don't remember.
>
>It was Rox or Nancy, I think, who dug this trick of mine when it was already months old (I mean, the message where I first described it), and then we talked about giving it a nice appearance.
>
>>Dragan. You usually have good tricks. Only now I find out they are indian :) Can you be more specific about the order/filter/group/format screen. Sounds good.
>
>The trick is older than UT (made it few years ago in FPD first), but on UT I've learned that that sort of tricks is called "Old Indian Tricks", so I joined the folklore :).
>
>The dialogue has two moverboxes, the filtering group, a combo to pick the report (if more than one is available) and a commandbutton to run the report, and, of course, a cancel button.
>
>The left listbox contains the names of columns to sort by. In my case, it's the production unit, account number, expense location, item. The user can move two or three of those into the right listbox (which is a moverbox) - this way they decide on the grouping.
>
>The filtering group is a set of pairs of textboxes; possible filters are set to field=lefttextbox.value) or between(field, lefttextbox.value, righttextbox.value); nothing is generated for the textboxes left empty.
>
>Behind the controlsource for the listboxes is an array, with three columns. First is the visible description in the listbox, second is the actual field name, and third is the column number of that field in the SQL select.
>
>Once the user clicks Print, it runs a SQL select first, and has a group by &lcGroup, which is usually something like "3,1,2", if third, first and second row of the listbox were moved. Also, it builds a couple of variables to show as group headers (to use for Eval(gr1), but also to print as a description, like Eval(txt1)+' '+eval(gr1) in the group header).
>
>I may send you the form, but it belongs to a class which is derived from a framework class, so it could probably have lots of unnecessary stuff - if you're ready for this, why not.