Hi Nadezhda!

I think the best way - use two or more grids in main report's form:
- grid with county
- grid with town...

User choose county, then he see towns in this county in another grid, choose it e.t.c ....

In the footer of the form you can place additional conditions - amounts (please do it like from ... to ...) or something else. Then you have to develope typical forms of the report with filter condition tha you will form from what your user choose.

I think it will be simply way and very flexeble. (Your users can add county as many as they wish)

Sergey

>Hi Vlad,
>
>In pur towns table we have field county (fullname) and ccode (county code). We also have registry, region, etc. Anyway, this is not enough, because our customers want to define their own regions. E.g. North MA, South MA, West Ma, East MA (just an example, not real regions). They select towns, which by theier opinion belong to the new defined region. They also have to set some Sort Order (how do they want this defined region appear in a report). They may assignorder to each town within region too (probably, I have to check the spec about it).
>
>Anyway, the idea is that customer would select towns from the list and define (describe) region.
>