I use only custom tag to contain information of the population of the Cities, Towns and Villages.

I have two questions concerning Custom Tags

How to avoid inheritance of one Custom tags by another one (it would be very good if we were able to choose how to handle inheritance of the properties of all the fields). For example I insert the population of the City as 2 000 000 and I have a workplace or House in this city which is subordinates to it because are located inside - so my house also has 2 000 000 persons!

Next question is consequent:

Is it possible to make one field value depend on another field value?

for example: I have population of the city 2 000 000 is it posible to set the value of object type as (City, Town, Village) because the field "population" is not empty and set this value depending of the rule (e.g. 500 000 and more - city, between 5 000 and 500 000 - town, less than 5 000 - village) automatically?

Not at the moment.  This feature will be available with macros.  You will be able to write a small script, typically one or two lines of code which will fetch data from other values.  We will also provide an interface with sample "scripts" so the user not knowing any scripting will be able to see how it works.

Here a sample code of such feature in the future.

If (Population > 500000) Then   Type = "City" Else If (Population > 5000) Then   Type = "Town" Else   Type = "Village" End If

Thank you for the quick reply.

I think that the Value should be turned on by Default (to Inherit) because it is visible that it is inherited and if it is turned out it is not visible.

By the way is it concerns only Custom Tags or all the Tags? Once before I mentioned in one topic that Comment is inherited in all the tabs - and it is still so.

By the way it may be possible to do something like enabling of the dependance if this feature is "on" for this field:

the field is "...DependentFieldValue..." if field "...FieldName..." equal/more/less/more or equal/less or equal/not equal/..."macro"

I understand that there can be more than one value in the dependent field and this probably has to be solved by macro but these methods could be combined and there could be a place for entering code if abovementioned types are insufficient

Thank you.

I have the feeling the places should inerit only a few fields.  What fields should be inherited (if any)?

Had a closer look at this and I think no field should be inherited. It is enough to report the parent place. However realized with regard to this another item, may be Ron can have a look at.

If I have a house in a village in a region in a state in a country, all places are reported several time in the places index. If a place has a parent place, there is no need to index the childrens place and so force, thus making the places index much shorther.In the attached sample only those reported under D (the top parent place) should be shown, since all other places are reported there.

I remember wondering about this when I wrote the code. I think a better solution is a compromise between the two. i.e. only show child places in a nested hierarchy if the indexed place does not itself have a parent place. This would show each place as an entry in the index as now but the hierarchy of just the the topmost places. e.g. Deutschland in your example. Each place except the topmost places would then have two entries in the index.

As regards inheritance, I don't see why address fields should not be inherited i.e. street, city, county, state, country & perhaps zipcode. This would save having to enter the full address of each place. I think by definition a child place shares the same higher level address components as its parent. These are the only fields that should be inherited.