Amazing how many inconsistencies you can find in a genealogical database. I would get rich if my users pay 1 cent per 'error'. But it is all for free, so never mind that. The point is this: everyone who has put a lot of effort in building up his/her database is upset when it appears to have more than just a few errors. And most recording programs do not do a very good job in verifying. Download Genealogica Grafica from http://home.versatel.nl/genealogicagrafica/ and see what it detects in your data. (You will need to export to a gedcom in order to interface with the program. It has been tested on gedcoms with nearly a million persons. It is fast!) Tests include: - link inconsistencies - loops - loose ends (unconnected groups of persons) - date inconsistencies - unlikely situations When you let the program produce a map of birthplaces, it will also find misspellings in placenames. And it will also make graphicals of trees, inbreeding patterns and relationships. The Help is extensive. Hope this is a useful aid. Tom

On Sun, 21 Oct 2007 18:36:20 +0200, Tom de Neef <tdeneef@qolor.nl> wrote: > Amazing how many inconsistencies you can find in a genealogical database. > Download Genealogica Grafica from > http://home.versatel.nl/genealogicagrafica/ and see what it detects in your > data. (You will need to export to a gedcom in order to interface with the > program. It has been tested on gedcoms with nearly a million persons. It is > fast!) This would be a good place to mention that it's a free download, and that it apparently only runs on windows. > Hope this is a useful aid. Looks impressive.

Looks very good Nice work Tom! "Tom de Neef" <tdeneef@qolor.nl> wrote in message news:471b8006$0$245$e4fe514c@news.xs4all.nl... > Amazing how many inconsistencies you can find in a genealogical database. > I would get rich if my users pay 1 cent per 'error'. > But it is all for free, so never mind that. > The point is this: everyone who has put a lot of effort in building up > his/her database is upset when it appears to have more than just a few > errors. And most recording programs do not do a very good job in > verifying. Download Genealogica Grafica from > http://home.versatel.nl/genealogicagrafica/ and see what it detects in > your data. (You will need to export to a gedcom in order to interface with > the program. It has been tested on gedcoms with nearly a million persons. > It is fast!) > Tests include: > - link inconsistencies > - loops > - loose ends (unconnected groups of persons) > - date inconsistencies > - unlikely situations > When you let the program produce a map of birthplaces, it will also find > misspellings in placenames. > And it will also make graphicals of trees, inbreeding patterns and > relationships. The Help is extensive. > Hope this is a useful aid. > Tom >

Tom de Neef wrote: > Tests include: > - link inconsistencies > - loops > - loose ends (unconnected groups of persons) > - date inconsistencies > - unlikely situations Any decent genealogy software will check for these and more (such as duplicate persons). What makes your software any better? Disadvantages appear to include; - only runs on one OS - inconvenience of exporting to GEDCOM - any errors found have to be corrected manually (in the master database) Doesn't sound that impressive, really. Peter

"peter" <nospamjynyl@yahoo.co.nz> schreef in bericht news:1193027685.463602@ftpsrv1... > Tom de Neef wrote: >> Tests include: >> - link inconsistencies >> - loops >> - loose ends (unconnected groups of persons) >> - date inconsistencies >> - unlikely situations > > Any decent genealogy software will check for these and more (such as > duplicate persons). > > What makes your software any better? > If you use a program that does decent tests, Genealogica Grafica may not offer you anything in this area. However... most programs don't. (Tests on gedcoms from Legacy, PAF, Aldfaer, BK, FTM, you name it: inconsistencies galore.) In the area of date consistencies, Genealogica Grafica will find _all_ inconsistencies (using an artificial reasoning technique). Here is an example, pulled from a gedcom produced by Family Historian: The person named Laurentinus is male. Neither birth nor death dates are recorded. Birth and death of his mother and father are not known either. But a grandmother on mother's side is born in 1603. Thus his mother must have been born after 1616. Therefore his birthdate can not be before 1629 (assumption that mothers are >=13 when delivering). Laurentinus has a child in 1635. Thus he must have been born before 1622 (similar argument). Hence one of the dates must be wrong since there is a contradiction: born <1622 AND born >1629. Often such discrepancies point to a link to the wrong child. > Disadvantages appear to include; > - only runs on one OS > - inconvenience of exporting to GEDCOM > - any errors found have to be corrected manually (in the master database) > Very true. Tom