You can start by fixing your database design. Storing multple peices of data
in a single fiield is not a good idea and you are now seeing why. The
preferred design would look more like:
san fancisco a
san fancisco b
san fancisco f
san fancisco z
etc.
If you store other pieces of data about the cities, then you need two
tables, the first table without the cityparts column that has a single row
per city, and the CityElements table that has multiple rows per city, with
the two tables related by city.
This design makes it easy to sort by element and see cities by element.
Unfortunately, your report requirement goes beyond the simple
a
san francisco
seattle
new york
b
san francisco
etc.
which report could be created in a couple of minutes. assuming that your
table design was fixed.
If you are locked into the table design, or your report requirements are
non-negotiable, you will need to use some VBA to achieve the required
result. I need to leave for work now but I will check back tonight and if
nobody has been able to help, I will take a stab at it.