Hmm. Every time I tried I found the tree structure was exported (thinking
specifically of web pages here) with the persons details marked as private.
I haven't done this for a bit so I will have another look.
Maybe I have the metric version......
Foxy
----Original Message Follows----
I'm not sure that is correct, as I just exported my file, telling legacy to
not export private people....and I then opened the file with genviewer....I
cannot find any of my private people....not even marked as private. They are
gone.
I even opend the gedcom file with a text viewer and I found none of the
names that were listed as private
So private data is completely chopped off with export....this is as long as
you tell Legacy to NOT export private people
Donna
-----Original Message-----
The private tag in Legacy isn't really what you think. I would have thought
that it doesn't send any info of private people. In fact it sends the info,
just marked as private. So the tree structure remains.
This can have some advantages depending upon where you are sending the data.
The best way is to use the private tag to set another tag. So tag everyone
who does not have private set. Let's say you use tag 3 for this. Then, when
you do a gedcom export or a web page make, only export people with tag 3
set. This will fix the problem.
The other issue is it is not possible to globally set the private tag. To do
this at present it must happen through Access. I have a file on my web page
about importing data from Generations into Legacy and I set the private tag
through Access. It is at www.foxcrofts.com under family tree if anyone is
interested.
In summary, use the private tag to set a normal tag and only export those
tagged people.
Legacy User Group Etiquette guidelines can be found at:
http://www.LegacyFamilyTree.com/Etiquette.asp
To find past messages, please go to our searchable archives at:
http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
To unsubscribe please visit:
http://www.legacyfamilytree.com/LegacyLists.asp
