Use of ** in prefix.

Question

The db_error 512 Separators in first name brings up quite a few profiles with ** in the prefix field. Does anyone know a reason why this may be?

I've been removing it from open profiles without a manager, since it does not seem like a valid prefix to me, but more like something someone put in as a reminder for themselves that the profile needs attention. Which it obviously won't get if there isn't a manager anymore.

Answer 1

In my personal database, I use an Asterix * in the suffix field to designate the one child in a family who is my ancestor. This makes it easier to navigate. So I suspect whoever imported the Gedcom does something similar.

Certainly remove it, because it definitely doesn't belong there.

Comments

ooh... that's a very interesting tip. hadn't thought of that.

Answer 2

I have not encountered that in the profiles I have worked on but I can see no reason not to remove it.