Search for content in message boards

Do you create just one family database OR a database for every family you're researching?

Replies: 11

Re: Do you create just one family database OR a database for every family you're researching?

Posted: 4 Jan 2013 11:44AM GMT
Classification: Query
You don't mention the factor that bears most on this subject. How many people are involved?

If you are talking about 100 persons per "family line", by all means keep them in one file is the best answer. You will get operational efficiencies because of centralized things like place names and common report formats and common sources, etc.

If, however, you are talking about 10,000 people per family line, one might want to keep them separate. This is because FTM gets real slow with a lot of people. I can't really say how many people it takes to get real slow. I would be inclined to put them together and when things start to get real slow consider splitting lines off with the Extended Family Chart.

By slow, I mean the time it takes to:

move to the next field when entering items and hitting enter
The index redrawing itself when switching to the Family tab of the People Workspace
The time it takes for a the cursor to become active after moving to a field.

etc
SubjectAuthorDate Posted
NorskyGal 4 Jan 2013 6:00PM GMT 
silverfox3280 4 Jan 2013 6:44PM GMT 
NorskyGal 4 Jan 2013 6:53PM GMT 
keithnuttle 4 Jan 2013 7:06PM GMT 
serenity20061 5 Jan 2013 9:56PM GMT 
NorskyGal 5 Jan 2013 10:12PM GMT 
tulrose 5 Jan 2013 10:26PM GMT 
silverfox3280 5 Jan 2013 11:08PM GMT 
NorskyGal 5 Jan 2013 11:16PM GMT 
Marco Scavo 6 Jan 2013 4:48AM GMT 
per page

Find a board about a specific topic

  • Visit our other sites:

© 1997-2014 Ancestry.com | Corporate Information | Privacy | Terms and Conditions