In that case, the report generator still reports that one of them is the "Oldest" and the other one is the "youngest". This is a mistake!!

I think that if there is no information about the year of birth of the entire siblings, and the "Children Order" feature on Genopro, has not been changed manually, this information should not be included in the report, because it is based on a random order that we add those children to the Genogram, and not based on facts.

1. If there are birth dates (or ages), that would determine child order

2. If a child order exists that would determine what is written in the report

3. Otherwise, simply state the names of the children (perhaps in alphabetical order), without reference to who is oldest and who is youngest.

Danny

If we know that a person has 3 children for sure, but we believe that he has another son, so we can mark the checkbox: "possibly more children", under the family properties.

The report generator still reports that "A is oldest of three children" without saying that there is possible for more children to that family.

I would say 99% of families have a valid child order even if if Family.Children.Order is empty.  The solution is having a checkbox like Unknown Child Order.

I also suggest that if the option "possibly more children" or the option: "to be completed", is selected, there will be a note of that issue on the report, like:  "A is oldest of three children (possibly more siblings) "

I agree that this is the most appropriate method of overcoming this problem, but

Might I suggest that the Family Properties dialog could be used, so that where Family Line field entered as "To be completed" refers to this incomplete information and hence the report writer could ignore child oder where dates are not present.

Poolzone  a mere cog in a revolution

I do Not agree. I think that The option "To be completed" may refer to many situations that you want to complete in the future about this family, and not just for the case that we know who are the children of a person (All of them), but we just don't know their order.

I was looking for a solution that would be easily and quickly implemented to overcome the problem.

I cannot think of any reasons that we would use the field entry 'to be completed' that would infer we know for sure the oldest or youngest child? Of course I don't know everything yet If the dates were entered then the probem does not arise, and the report is correct relative to 'known' children.

Perhaps we might need a temporary fix to this problem, by adjusting the report before programming fixes sometime in the future. But I do agree that in the long term that a field should be allocated to suggest that all children are present.

Poolzone  a mere cog in a revolution