[Living] Person can not be set to start person of family tree report of ancestors

Wen I try to generate a Graphic family tree of ancestors, a particular person fails: “Person I0003 is not in database”. Many other people succeed and there is nothing special in that person.

I have performed various family tree repair runs without any change. What to do?

In my Ubuntu I have GRAMPS: 5.1.5
Python: 3.10.12 (main, Feb 4 2025, 14:57:36) [G…
BSDDB: 6.2.9 (5, 3, 28)
sqlite: 3.37.2 (2.6.0)
LANG: fi_FI.UTF-8
Käyttöjärjestelmä: Linux
Jakelu: 6.8.0-59-generic

Terve Juha!

I assume you are trying to run Reports > Graphical Reports > Ancestor Tree.

I got the same error when

  • the root person is marked private
  • the setting “Include data marked private” is unchecked (in “Report Options (2)”)

Is I0003 marked private? Another possibility is that the person is alive and living people are not included in the report.

cheers
Kari

1 Like

It seems like this could affect a number of reports. Perhaps a “placeholder” option for necessary connecting people (who are Private, Living or otherwise filtered out) could be created?

An example where this would be useful is for a Fan chart report for a living person. If the living person had a placeholder at the center, then the same Fan Chart report could be used for the siblings.

Yes, he is a living person. I created a dummy, dead person, who had same parents and got a graph. Thank you!

There is another problem with reports, when a family seemed to have only one child as the others are alive. Luckily I didn’t publish the report before I noted that (and cleared the ‘only’ child).

I think, there was no warning of missing data! I would suggest, there should be an empty box (or mention ‘N other children’) in the graphs and reports.

1 Like

There is another case where a dummy, dead person must be created–when creating a pedigree for newlyweds. It would be useful to ne able to optionally start with a “Family”

Also… if there must be an error message, maybe it could be less misleading?

“Person I0003 is not in dataase” is inaccurate. They are in the database (unless maybe this looking at a proxy database?). Maybe the message should be :
“Person I0003 is not in the filtered database”