Re: Importing to Legacy (Access) with problems...

Found it - knew it was there somewhere

Importing Rules:

If you don't want to have Legacy format your names and locations when you do
an import you can uncheck the box Format Names and Places (Init. Caps, UPPER
CASE, etc) and then Legacy will leave the names exactly as they are found in
the GEDCOM file. If you checked this option then Legacy uses the current
formatting options you have set in Options, Customize.

All Rights Reserved

Helen
"Paul Blair" <pblair@xxxxxxxxxxx> wrote in message
news:44431240$0$7599$afc38c87@xxxxxxxxxxxxxxxxxxxxxxx

Out here in the vast Australian continent, we have some states and
territories. We usually abbreviate these when we write - well, I do. New
South Wales becomes NSW, South Australia becomes SA, Western Australia WA,
Victoria becomes Vic and so on.

As long as we are working on the original file, things are fine. But when
we export them from, say, another program, then import them, things go
awry. At the moment, I'm converting a large file to Legacy.

After import, NSW become Nsw, SA becomes Sa...and New Zealand, normally
NZ, becomes Nz. WA stays as WA - and, as there is no preset place table in
Legacy, I wonder why it remains the same. Its not getting mixed up with
Washington State, USA is it?

Looking at the GEDCOM file, it gives NSW (not Nsw) and so on, so the
change is being wrought upon import.

The sensible thing to do would be to spell everything in full, but as this
is not the norm for pretty much anything, most of us don't do that. So the
only way I can see to fix this is to open the tables in Access and do
find/replace - as the present problem runs to about 30,000 changes, I'm
not going to wade through a Legacy edit screen.

Does anyone else from Oz....or another country...have this problem? Has
anyone found a good way of filtering this problem out (Legacy gives you
some import filters, but nothing that will deal with this one!)

Paul


.

Relevant Pages

  • Re: The future for Legacy?
    ... Since I started using Legacy, however, I've been using fewer programs. ... FHS, because Legacy could do most of the things that they did. ... MARRIED 20 Aug 1879 in Adelaide, SA, to THWAITES, Walter William ... MARRIED 9 Jan 1858 in Gundary, NSW, to FRANCIS, Alfred John ...
    (soc.genealogy.computing)
  • Re: Importing to Legacy (Access) with problems...
    ... South Wales becomes NSW, South Australia becomes SA, Western Australia ... I'm converting a large file to Legacy. ... anyone found a good way of filtering this problem out (Legacy gives you ...
    (soc.genealogy.computing)
  • Importing to Legacy (Access) with problems...
    ... New South Wales becomes NSW, South Australia becomes SA, Western Australia WA, Victoria becomes Vic and so on. ... WA stays as WA - and, as there is no preset place table in Legacy, I wonder why it remains the same. ...
    (soc.genealogy.computing)
  • Re: Importing to Legacy (Access) with problems...
    ... New South Wales becomes NSW, South Australia becomes SA, Western Australia WA, Victoria becomes Vic and so on. ... WA stays as WA - and, as there is no preset place table in Legacy, I wonder why it remains the same. ...
    (soc.genealogy.computing)
  • Re: Importing to Legacy (Access) with problems...
    ... Somewhere in Legacy there is a thingo that tells Legacy to leave it as you ... South Wales becomes NSW, South Australia becomes SA, Western Australia WA, ... anyone found a good way of filtering this problem out (Legacy gives you ...
    (soc.genealogy.computing)