Hi Sergey,

BTW, no one is US can spell (or pronounce) my full first name correctly, so I shortened it :)

You probably slightly misunderstood the problem. The customer (or user) should be able to create their own regions, which are not related with county. IOW, they define region1: Town1, Town2, Town3; region2: Town4, Town5, etc.

My first little problem: how would I store this info? In two related tables:

Parent: RegionID (Unique generated), CustomerID, RegionCode Char 2, Region Name
Child: RegionID Town City ccode County (just in case).

Then on the form I would have Textboxes for Region definitions and Mover list box for selecting towns.

I was also thinking about Cetin's Multiselect Grid, but I'm not sure, how to organize drag/drop functionality here and I don't want to complicate my life, if it's tough (I'm not sure).

If I would use this model, I have to create a cusror with Region/Town before executing query from the Main databases.

Basically, these are my ideas till now.
>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.
>>