Locations: building & floors

[#1]

Whenever I think that there's a better way, usually there is... I'm thinking that the issue of buildings and floors -must- have been dealt with before. I can't figure out "Advanced Reference Qualifiers". I think that simply using locations & parents would be fine BUT I can not figure out how to show the parent of the location.

We've set up our "Locations" so that each location is a building.
We'd like to have floors associated within each location like so:
Wall St office (Location)
15 (floor)
16 (floor)
Broadway office (Location)
2 (floor)
15 (floor)
What's the right way to do this...?
I would like this data to reside in cmn_locations, but display on a User record so that we know where a person's building and floor is. We'd also like to show the Caller's office & floor on an Incident. It seems pretty basic, but darned if I can figure it out.
And evenutaully, we'd like to add rooms to the floors like so:
Wall St office (Location)
15 (floor)
rm108 (room number)
rm109 (room number)

[Valor1]

This is a known issue with using calculated fields.
The problems is that field calculations only get saved when a record is updated in the DB. So if you've JUST added a calculation, and it it as the display value for the reference, you'll see "Blank" display values and you won't be able to use typeahead matching until the records actually change, and get updated in the DB.

To get these values populated, the easiest way is to "Update All" records in a list, modifying a field that has no data or is inconsequential. On tables with an "active" flag, I use it, toggling off and back on again.