If you do the rename in the Picture Center within Legacy, all links to
that file should be updated.
If you do the rename outside of Legacy, you would need to relink every
occurrence.
Hope this helps.

On Mon, Apr 20, 2009 at 2:23 PM, Brian Beddor <bbed...@japsolson.com> wrote:
> Welcome back!!!
>
> I think I'm pretty much doing it as you do.
>
> If I have sources/records for a child and I don't know if that child
> ever got married then I treat him/her as unmarried and use the parents
> MRIN.  If I latter find out the child did marry then any records after
> the marriage I put with the child's MRIN.  However, I have not been
> going back and re-numbering the child's records from the parents' MRIN
> to the child's MRIN.  I'm a little nervous about how the linking works
> with Legacy. If you rename a document do you have to go and find all the
> places in Legacy where it was used and change the name?  Or, does Legacy
> somehow track when we rename a file?
>
> Thanks for the feedback and advice,
> Brian
>
>
>
> -----Original Message-----
> From: k...@legacyfamilytree.com [mailto:k...@legacyfamilytree.com] On
> Behalf Of JLB
> Sent: Sunday, April 19, 2009 9:09 PM
> To: LegacyUserGroup@legacyfamilytree.com
> Subject: [LegacyUG] Attn: Brian Beddor & Laurence E. Stephenson
>
> I heard you talking about me so I resubscribed.  I got a new job so I've
>
> been away from this for what seems like months and I'm a bit rusty.
>
> I put all documents for unmarried children with their parents.  For
> children who marry I put all their documents, including childhood ones,
> under their own MRIN.  Anything that's an individual record like a birth
>
> certificate, but not the census records that would be filed under one of
>
> the parents.  Maybe this is the wrong way to do it?  If a person
> remarries, obviously they would have a second MRIN and all documents
> pertaining to the marriage and events after the marriage go there.  So
> apparently there's a difference in our methods but I don't know if it
> matters.
>
> What happens with children where they might have been married but I
> don't have that information yet?  Well, for starters I regard them as
> unmarried and all their information goes with the parents.  If later I
> find out they were married, I have to move some things. At least I don't
>
> have to go far to find them.
>
> I used to put MRIN's in the Individual Information User ID fields as a
> kind of backup and also because I could sort the Name List by User ID,
> i.e. MRIN's.  Then I moved them all to the Marriage Information Screen
> which has also has a box for User ID and all things considered, that one
>
> makes more sense, but it doesn't work in the Name List, at least didn't
> the last I looked.
>
> -----
> JL
> JLog - simple computer technology for genealogists
> http://www.jgen.ws/jlog
>
>
>
> Legacy User Group guidelines:
>   http://www.LegacyFamilyTree.com/Etiquette.asp
> Archived messages:
>   http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
>
>
>
>
>
> The information contained in this message is confidential. If you are not the
> intended recipient, dissemination or copying of this information is 
> prohibited.
>
> If you have received this communication in error, please notify the sender and
> delete the message from your system. Thank you.
>
>
>
>
> Legacy User Group guidelines:
>   http://www.LegacyFamilyTree.com/Etiquette.asp
> Archived messages:
>   http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
>
>
>
>



Legacy User Group guidelines:
   http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages:
   http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp



Reply via email to