1) Right click anywhere on the toolbar - The "Customize Main Toolbar"
window opens.
2) Drag any button from "Available Toolbar Buttons" to the "Main
Toolbar" area of the "Customize Main Toolbar" window.
You may be tempted to drag it all the way to the top toolbar. Don't.
3) Click OK and they should be there.

Harvey

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Karen
Ver Wayne
Sent: Saturday, June 14, 2003 12:26 AM
To: [EMAIL PROTECTED]
Subject: RE: [LegacyUG] Location Icon on the Tool bar...WOW!!!


I can't get it to work.  I drag the icon but nothing appears.   Karen

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Sandra
Duncan
Sent: Friday, June 13, 2003 2:01 PM
To: [EMAIL PROTECTED]
Subject: [LegacyUG] Location Icon on the Tool bar...WOW!!!


Hello again
    I just discovered something very fabulous in LEGACY I right clicked
on the tool bar and was able to add an icon to the bar for LOCATIONS
!!!!! I was going to suggest that the next version included an easier
way to access this feature, Good Golly this is an awesome program
Happily going for the big merge thing Sandra

Good places to visit!!
# 1.  http://www.mudcreek.ca/  <=Makes readable gedcoms for the
genealogically challenged # 2.
http://www.ancientfaces.com/cgi-bin/index.cfm
#3. http://www.gencircles.com/users/purplevw1/1
  regards
SANDRA IN SACRAMENTO
[EMAIL PROTECTED]
----- Original Message -----
From: "Jeremy Main" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 12, 2003 7:41 PM
Subject: Re: [LegacyUG] Merging


> Sandra:  Some thought on your merging proposition:
> 1) Definitely do backups and make a detailed gameplan before 
> beginning.
> 2) Start by converting the FTM file into a Legacy file in it's own
right,
> separate and independent from your existing Legacy database.
> 3) Compare the two files: go to Tools / Compare Two Files for
Duplicates
> 4) Use all the various results and reports from step #3 to plan out a
course
> of action.
> 5) Do a number of practice merges on separate copies of your data to 
> learn about the ins and outs of merging.  There are many issues.  
> Consider these "throw away merges" because they are just practice.  
> You'll use them to
find
> out what can happen during merging.  You'll note on the  Merge/Find 
> duplicates/Normal Duplicate Search screen there are many options.
> 6) Merging can be very tedious especially if your being very careful 
> and
not
> using AutoMerge.  On files the size of yours it would be impractical 
> (on your personal time) to attempt to do it all at once.  I'd break it

> down
into
> a lot of independent lines, hopefully of less than 1,000 individuals 
> each (maybe even just 500 or so).  Then do each one of these 
> independently.
> 7) Once you've broken down the project into independent files (family
lines)
> of 500 or less,  then check out the Legacy feature of:  View/Split
Screen
> View.   This feature allows you to have two separate Legacy files open
at
> once and view them side by side.  (It's really nice if you have a dual

> monitor system and enlarge the main window across both screens, then
each
> Legacy file will be on a screen by itself.)   From this view, you can
easily
> compare families and individuals.  You can also drag and drop from one
file
> to the other and do spontaneous merges, but on a targeted, individual 
> by individual basis.
>
> As you put together your gameplan, ask yourself a number of questions:
> a) Are most of the individuals duplicates?  If so, do you already have

> all the data on these individuals in both files?  If so, why are doing

> a merge (on these individuals) since there's no gain and plenty of 
> potential for things to go wrong?
> b) If you're trying to add missing individuals (and their data) to the

> Legacy database,  why not research out this particular list of people 
> out and just merge them?
> c) Have you used the "User ID Number" in both files?  And can you use 
> this to guide your merges in an unambiguous fashion?
> d) Do both files use the same RIN numbers on your individuals?  If so,
this
> can be used during comparisons and merges to good advantage.
> e) What is the state of Sources and Source citations in both files and
what
> do you want to end up with?
> f) What is the state of the various textual notes in both files.  
> Merging can easily make double copies of all your notes.  Or it can 
> just as easily not merge in the notes from the second file.  This has 
> to be planned for.
>
> Have you read the excellent white papers on merging at the Legacy web
site?
> Or reviewed the teaching CD-ROMs on this subject?
>
> One adage I've taken to heart on merging:   Just because you CAN merge
(with
> Legacy's excellent capabilities), doesn't mean you SHOULD merge.  It
really
> takes a lot of thought and planning for the end result to be what you
want.
>
> Hope these opinions are helpful,
> Jeremy Main,  Bethesda, MD
>
> ----- Original Message -----
> From: "Sandra Duncan" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, June 12, 2003 7:57 PM
> Subject: [LegacyUG] Merging
>
>
> > Right now I have 52,901 persons in my LEGACY data base but I want to

> > go
> for
> > a final merge  [FROM] my FAMILY TREE MAKER [HAS 54,700]before I can
> breathe
> > a sigh of relief.
> >     As you may remember, I am a very recent convert to LEGACY found 
> > more
> new
> > great features today & I also found an old LEGACY, disk ,the old  3 
> > 1/2" size but that was even before my cousin bought my new computer 
> > for me at
a
> > computer show   7 March 2000 and placed Legacy on it for me....All I
ever
> > did was to find out that it was great for merging things (YES, I AM
SLOW)
> > but now I have this massive task of combining everything into 
> > LEGACY,so,
I
> > need to know the very best way, I have 180 gigabytes worth of 
> > harddrive space and a CD burner so now all I need is help  like I 
> > was a Newby
please
> > NOTE: There will be many less persons once I do the merge of the 
> > LEGACY
&
> > the FTW
> > HELP PLEASE
> >
> > Rootsweb.com Admin: {for} Caplinger,Duncan,Forsythe, Mounce,  
> > Schoonover,Tyler,Vanscoy,Wilmoth
> >
> > Sandra Tyler Duncan
> > [EMAIL PROTECTED] http://www.gencircles.com/users/purplevw1/1
> > *-* THE GREATEST*-*
> > http://www.progenealogists.com/genealogysleuthb.htm
> > ================================
> > Work like you don't need the money.
> >  Love like you've never been hurt.
> >    Dance like nobody's looking.
> >
> >
> > 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
> >
>
>
> 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


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


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

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

Reply via email to