Jump to content


Member Since 05 Dec 2018
Offline Last Active Jun 10 2020 09:20 AM

Topics I've Started

Dev Management Request

03 December 2019 - 11:47 AM

We are at a critical time in genealogy software development as all the major players are releasing major versions.  Thus this is a great time to be searching for a new app to maintain your genealogy data for years to come.  That is where I find myself today.  I have been testing software going on a 15 months.  My tree has over 27K records, 10K Families, 20 Repositories, 5K media files, 7K places and 9K citations.

  • Roots Magic 8
  • Family Historian 7
  • MacFamily Tree 9
  • Family Tree Maker 2019
  • any many more


I don't include Legacy 9 here because I consider it a dead product and a product without future is not one that should be considered as a future product.  Some may argue otherwise as Legacy 9 has managed to keeps the hopes of Legacy 10 as a possibility and we might one day even see it, but Legacy 11 is certainly never going to be seen because why would MyHeritage invest development money on two products?  No logical business entity would ever do this for more than one generation.


After all my testing and it has been lots of work, I have come to the conclusion that on the mac platform MacFamily Tree 9 reigns supreme and unchallenged natively.  On a PC, Roots Magic and Family Historian are the leading products.  In fact, the two products are complimentary in that what one product does great, the other needs a lot of work.  I find myself debating privately that if I could only take the two products and merge them into one while taking the best feature implementation, I would have one hell of a product.  That is only a dream, so I am left with asking the question, "Which product should I chose to manage my tree and others moving forward?"


I can't answer this question though because both developers will not post the features included in the next release.  I know what you are thinking, this is good business as no one should give their competitors a list of how their product is better.  I would argue that you would be wrong.  Ideally, both products are expected to actually release in the next three months baring setbacks.  So product features should be locked.  In fact, developers should be finalizing code and fixing bugs detected by test cases at this point.  So there really is no point in not releasing  what features with pictures we can expect.  I know, your asking what if a feature requires too much work to finalize and has to be dropped to a service pack addition?  My answer is that this happens all the time.  In fact, good developers are constantly working with consumer testers and consumers in general.  They share product futures because that is how the maintain and attract new customers like me who are searching for a new home.


I don't care about waiting or having to use a test build.  What I care about is being able to make a decision or at least to have some direction.  It is okay and even reasonable to migrate to an existing version of a product while waiting for a future release provided you have a clue what that future release is going to do.  Will it fix the weaknesses of the product and add features that makes it more desirable?  Very few of us know the answer to this question, which places us in the uncomfortable position of having to set aside our genealogy work.  Yes, genealogy is generally a pastime for most.  For me it is not.  I work on my genealogy every day and when I am not working on mine, I am helping others. 


Therefor, I would like to ask Roots Magic to make these features public and if it wont do that, then at least allow me the opportunity to sign a "No Release Form," and provide me with a test copy.  I am more than skilled to provide feedback as I retired from Microsoft where I worked as a developer and up.


I can be reached via this forum or by email associated with this account.

Routine Data Maintenance?

29 November 2019 - 09:09 PM

So I find my genealogy comes in ebbs and flows even when working consistent hours. No matter how hard you try to maintain normalized data (1 fact) you always seem to end up with duplicates, and variants. So you have to spend some time on data maintenance with the goals:

1. Normalization
2. Handling Duplicates and Variants
3. Consolidation and sometime bifurcation
4. Re-categorization

You really cant get away from doing these and more activities every now and then unless you just want your database of your family tree to be more like your family weeds.

Unfortunately, RM appears to struggle in this area greatly unless I am missing something. Yes you can merge duplicate people and places which is a good start. But what if you end up with two facts that seemed to diverge in content but after further consideration you decide they should be one type. The answer of manually going to each fact/event or whatever you choose to call it and add a new item using the consolidated type and delete the old seems to be very painful especially when a merge type feature would resolve the problem.

So how can I achieve this kind of maintenance using RM? Does anyone know if this feature is included in RM8?

SQLLite Tools for Roots Magic Password Prompt

24 November 2019 - 06:22 PM

Following instruction to open RM dB for my first try on a backup database and I keep getting prompts for a password?

Question- RM to Ancestry Only

19 February 2019 - 05:23 PM

Can RM be configured to only push updates to ancestry. In short, I only want to push my updates. I dont want any ancestry.com Gremlens sneaking into my tree:(

Which U.S. census Template

18 February 2019 - 10:28 PM

I have been working hard to make some serious changes in my genealogy work. One of the biggest is the adoption of the Evidenced Explained Style of Citations.

I want to have all my U.S. census citations and Bibliographies look like what is described and shown here but for U.S. not Canada. What template short of making my own gets me closest to this? https://www.evidence...QCsample254.pdf

In short I the following:

Source List Entry:
[State]. [County]. [Year] U.S. census, population schedule. Digital images. [Web page title]. [URL] : [year accessed].

Missouri. St. Louis City. 1920 U.S. census, population schedule. Digital images. Ancestry.com. http://www.ancestry.com : 2011.

[Year] U.S. census, [County name] County, [State], population schedule, [Civil Division (ward, township, town or city)], enumeration district (ED) [number], sheet [number] (stamped, [number] handwritten], dwelling [number], family [number], [Person or persons]; digital image, [Web page title] ([URL] : accessed [date]); citing NARA microfilm publication [number or letter], roll [number].

1920 U.S. census, St. Louis city, Missouri, population schedule, ward 3, enumeration district (ED) 51, sheet 5A (handwritten, 111 stamped), dwelling 70, family 106, John XYZ; digital image, Ancestry.com, (http://www.ancestry.com : accessed 24 September 2011); citing NARA microfilm publication T625, roll 948.

[Year] U.S. census, [County name] Co., [State abbreviated], pop. sch., [Civil Division], ED [number], sheet [number] (stamped, [number] handwritten], dwell. [number], fam. [number], p. [number], [Person or persons].

1920 U.S. census, St. Louis city, Mo., pop. sch., ward 3, (ED) 51, sheet 5A (handwritten, 111 stamped), dwell. 70, fam. 106, John XYZ.