|
Finding Family Relationships in Access genealogy dbase
Fri, 24 Nov 2006 16:21:50 +1030
soc.genealogy.computing
previous
Ray Murphy...
Paul Blair...
|
I'm not at all sure what you mean. Legacy stores data at pretty much
first principles level, leaving the door(s) wide open for personal
efforts. You can build anything you want from that, provided the data is
in a table or tables, and there is a means of relating one table to
another. The systems are designed primarily for genealogy.
|
|
I've converted a gedcom file to an MS Access database via the GED2CSV
program and got some good things happening with it, but I haven't got a clue
how to connect people with relatives. For example, I can see in the
'Relations table' where married couples are 'connected', but I can see no
connections between children and parents, and grandparents etc.
Any ideas?
Dave Mayall...
|
Yes.
Use something designed for the job!!
Ray Murphy...
keithm...
|
Hi Ray,
I'm the author of Ged2Csv, so I'm quite familiar with the output
format. I'd me more than happy to help you with the SQL you'll need to
connect all the various bits of information. If you are familiar with
PHP, you should be able to pick out what you need from this file:
If you need more help than that send me an email at
keithm@infused-solutions.com.
Cheers,
Keith Morrison
|
|
RM: Presumably you mean a genealogy program, but they are not designed to
query and display any data in my database - such as displaying a table
containing the basic data for all children and great grand parents in
consecutive lines.
T.M. Sommers...
|
Take a look at Lifelines. It has its own report-generation language.
Ray Murphy...
Charlie Hoffpauir...
|
Import the GEDCOM into a genealogy program that doesn't use a
proprietary file format (Legacy, Rootsmagic, The Master Genealogist
for ex.) and then import/convert the database files to Access.... then
operate on them in whatever manner you wish.
Ray Murphy...
|
RM: Excuse my ignorance here, but I assume you mean - import a gedcom into a
genealogy program that uses a *standard* gedcom format.
Dennis Lee Bieber...
|
No, he meant what he said... Use a genealogy program whose NATIVE
data format is openly documented, or otherwise directly accessible using
non-genealogy tools. Legacy uses M$ JET database engine (its .FDB files
are essential .MDB files with a different name, and no forms/reports
internal); TMG uses Visual FoxPro format (and these, via ODBC drivers,
can be imported directly into a JET database). JET is the native
database engine used by M$ Access -- so the import can be done via
Access commands.
For all practical purposes, there is no "standard" GEDCOM unless you
restrict yourself to ONLY the data used by the LDS (who produce PAF, as
I recall).
|
|
Or, with the more versatile programs, create a custom report in the
program that gives you the data you want, and import that report into
Access.
Charlie Hoffpauir
Ray Murphy...
|
RM: At this point I think I want to import *everything* from a gedcom into
Access (to be able to tap into it); so I cannot see any advantage in any
type of selective filtering, but there may be advantages in what you are
suggesting that I am oblivious to.
Hugh Watkins...
|
merging gedcoms tends to make one big soup
a mess with much duplication
I only ever import data I have totally reviewed person by person
I find FTM 16 is adequate for my own use
I purchased Custodian 2 and 3
but could not be bothered with reentering all my data
and Custodian 3 is a database with a very useful range of templates
so why are you reinventing the wheel?
Hugh W
|
|
http://freepages.genealogy.rootsweb.com/~charlieh/
|
|
RM: I tried to download it but nothing happens.
|
|
|
|
|
|
