GENBOX-L Archives

Archiver > GENBOX > 2003-08 > 1060923660

From: "Beth Gay" <>
Subject: Re: [GENBOX] Merging Databases (wiping out places: caution)
Date: Fri, 15 Aug 2003 00:01:28 -0500
References: <> <001701c362d5$8cd596f0$0100a8c0@beth> <000101c362e1$3ed4e850$4240880a@BILLXP>

Thanks very much for the detailed explanation and advice and especially for
taking the time to respond. I will replace all of the places; I will
probably cite more places throughout the world; than I originally thought
about. I have many relatives that served in World War II in various places
in the European and Pacific fronts.
I hope that you are planning to have your fantastic program on display at
the upcoming APG Professional Management Conference in Orlando.
Kindest regards,

----- Original Message -----
From: "William T. Flight" <>
To: <>
Sent: Thursday, August 14, 2003 10:44 PM
Subject: Re: [GENBOX] Merging Databases (wiping out places: caution)

> Hi Beth,
> A word of caution about wiping out the default set of place names.
> Unlike nearly every other genealogy program, places in Genbox are not a
> simple "flat" list. They form a hierarchy, with lower place levels linking
> to higher place levels, leading up to nations. This organization has
> advantages--for speeding data entry, advanced query capabilites, applying
> filters, formatting options on reports, and more.
> When importing data, Genbox attempts to link new place names into the set
> place names already known. It accomplishes this primarily by working
> top-down, starting with the nations, states, and other names that it
> recognizes, linking new place names beneath. It attempts to identify the
> place levels of each comma-separated place name part (local site, city,
> township, county, state, nation).
> An essential part of this operation is the database itself: it uses the
> stored place names as the base on which to build. There is no storage of
> place names other than what is in the database. When all of the place
> have been removed, Genbox won't know Utah from France. The place hierarchy
> that results from a GEDCOM import will likely by poorly organized: some
> states may become countries or counties, local sites might be labeled as
> cities, there may be a nation "United States" with 500 links below and
> another nation "USA" with 700 links below, including both states
> and "IL" in each, with their own lower levels.
> When entering places manually, you can use the Magnify Place Dialog to
> position each part at the correct level. If you plan to enter all of your
> data that way, I don't see a problem, other than it will be tedious. <g>
> concern is rather that a GEDCOM import with an empty place database will
> give you satisfactory results. (Of course, if your GEDCOM has mostly Asian
> or African place names, the default hierarchy won't be much help anyway.)
> My recommendation is to keep the default place names--at least the nation
> and state levels. If you find their presence in your database distracting,
> we can probably think of more creative ways to "hide" them from view.
> Perhaps some new filtering capabilities will do the trick...
> Best regards,
> --Bill
> William T. Flight
> ----- Original Message -----
> From: "Beth Gay" <>
> To: <>
> Sent: Thursday, August 14, 2003 10:32 PM
> Subject: Re: [GENBOX] Merging Databases
> > But back to what I am trying to do. I created a new database without the
> > places so I wanted to open that database and my initial Coker database
> > place the names, sources, etc. in the new database but not the places
> > reenter the places. I am not fond of typing so I thought that I could
> > and drop but I guess cut and paste will work just as well. There may be
> > problems with this idea, so let me know. I could work on my places in my
> > present database and export the file to a GB-file and rid myself of the
> gaps
> > in the places as Wim suggested.
> > Beth

This thread: