A family of Microsoft relational database management systems designed for ease of use.
Do you have some good reason to store this field in a table, as opposed to just displaying it for the user? It would appear to violate two basic relational principles: that fields should be "atomic", storing only one piece of information (you're concatenating six), and - even more important - that data should not be stored redundantly! If this combined "location" can always be derived from the six fields in the main form's table, then it should simply not exist, since you can always generate it as needed.
If, on the other hand, it's a true default - you will often or usually store that string, but allow the user to edit it at will - you may want to use VBA in the Subform's BeforeInsert event to generate it. That would still be questionable in my opinion (not atomic and partially or totally redundant)!