<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Family Tree Maker 2009: Minor Update</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2009/05/05/family-tree-maker-2009-minor-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2009/05/05/family-tree-maker-2009-minor-update/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=family-tree-maker-2009-minor-update</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Tue, 21 May 2013 21:32:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Tony Cousins</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/family-tree-maker-2009-minor-update/#comment-38380</link>
		<dc:creator>Tony Cousins</dc:creator>
		<pubDate>Mon, 18 May 2009 21:49:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1189#comment-38380</guid>
		<description>Hi Michelle

Not wanting to put words into the mouth of other people - but I think Tony #81 is complaining that he had to provide a credit card in order to get the &#039;free&#039; trial membership.

This is nothing new, in fact it has been a &#039;problem&#039; for a number of years and the source of some legal battles with Ancestry.

It does seem strange that this is a requirement to gain a free trial.

I&#039;m not worried - I&#039;ve been a paying subscriber for a number of years :)

TonyC</description>
		<content:encoded><![CDATA[<p>Hi Michelle</p>
<p>Not wanting to put words into the mouth of other people &#8211; but I think Tony #81 is complaining that he had to provide a credit card in order to get the &#8216;free&#8217; trial membership.</p>
<p>This is nothing new, in fact it has been a &#8216;problem&#8217; for a number of years and the source of some legal battles with Ancestry.</p>
<p>It does seem strange that this is a requirement to gain a free trial.</p>
<p>I&#8217;m not worried &#8211; I&#8217;ve been a paying subscriber for a number of years <img src='http://blogs.ancestry.com/ancestry/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>TonyC</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michelle Pfister</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/family-tree-maker-2009-minor-update/#comment-38378</link>
		<dc:creator>Michelle Pfister</dc:creator>
		<pubDate>Mon, 18 May 2009 20:06:53 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1189#comment-38378</guid>
		<description>Barbara #82,

The ability to include non-preferred facts will be part of the next FTM release. Also, merging of duplicate facts is somewhat supported in the current product.</description>
		<content:encoded><![CDATA[<p>Barbara #82,</p>
<p>The ability to include non-preferred facts will be part of the next FTM release. Also, merging of duplicate facts is somewhat supported in the current product.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michelle Pfister</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/family-tree-maker-2009-minor-update/#comment-38377</link>
		<dc:creator>Michelle Pfister</dc:creator>
		<pubDate>Mon, 18 May 2009 19:55:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1189#comment-38377</guid>
		<description>Tony #81,

If you did not intend for your subscription to auto-renew and you are not using it, you can cancel it by calling 800-ancestry.</description>
		<content:encoded><![CDATA[<p>Tony #81,</p>
<p>If you did not intend for your subscription to auto-renew and you are not using it, you can cancel it by calling 800-ancestry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eydie Keim</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/family-tree-maker-2009-minor-update/#comment-38370</link>
		<dc:creator>Eydie Keim</dc:creator>
		<pubDate>Sun, 17 May 2009 22:47:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1189#comment-38370</guid>
		<description>On May 6 (reader # 8)I wrote about the Chronological facts displaying incorrectly in individual report”  and you responded with:
The update involved the individual report rather than the simple register. Since the simple register does not have the “sort chronologically” option, that type of sort is not supported in the 
simple register.

My next question is why not? It just seems that it would be the natural order of events. 
The Register report lists in chronological order so why not the Simple Register.</description>
		<content:encoded><![CDATA[<p>On May 6 (reader # 8)I wrote about the Chronological facts displaying incorrectly in individual report”  and you responded with:<br />
The update involved the individual report rather than the simple register. Since the simple register does not have the “sort chronologically” option, that type of sort is not supported in the<br />
simple register.</p>
<p>My next question is why not? It just seems that it would be the natural order of events.<br />
The Register report lists in chronological order so why not the Simple Register.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barbara Cunningham</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/family-tree-maker-2009-minor-update/#comment-38369</link>
		<dc:creator>Barbara Cunningham</dc:creator>
		<pubDate>Sun, 17 May 2009 17:08:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1189#comment-38369</guid>
		<description>I&#039;d like to see in future updates the ability to include non-preferred facts in the reports, as well as the ability to merge duplicate facts.</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to see in future updates the ability to include non-preferred facts in the reports, as well as the ability to merge duplicate facts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/family-tree-maker-2009-minor-update/#comment-38368</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Sun, 17 May 2009 14:56:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1189#comment-38368</guid>
		<description>Why don&#039;t you give me what I bought without forceing me to signup to by more. I bought your family tree maker deluxe and was told I would have a three month membership,  thats what  I want and then I will decide if I want more. You miss represented your product. I bet you don&#039;t read these either, much less respond ! Maybe the folks reading it will respond to it though.</description>
		<content:encoded><![CDATA[<p>Why don&#8217;t you give me what I bought without forceing me to signup to by more. I bought your family tree maker deluxe and was told I would have a three month membership,  thats what  I want and then I will decide if I want more. You miss represented your product. I bet you don&#8217;t read these either, much less respond ! Maybe the folks reading it will respond to it though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Ralston</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/family-tree-maker-2009-minor-update/#comment-38364</link>
		<dc:creator>James Ralston</dc:creator>
		<pubDate>Sat, 16 May 2009 18:32:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1189#comment-38364</guid>
		<description>#78 Michael
This may not help you, but it sure took care of my FTM 2009 from crashing. Go to the &quot;EDIT&quot; tab, click on find duplicate people and eliminate the ones you clearly know are wrong. Once I did that, my program didnt crash any further. This bunch at Ancestry are clueless about telling people remedies, unless they get so many complaints, that confuses them. They put out patches that screw stuff up or ones that certain people cant even get, try to fix things that are not broke, and give us new stuff, that we clearly tell them we dont like. Give it a try, what the heck.</description>
		<content:encoded><![CDATA[<p>#78 Michael<br />
This may not help you, but it sure took care of my FTM 2009 from crashing. Go to the &#8220;EDIT&#8221; tab, click on find duplicate people and eliminate the ones you clearly know are wrong. Once I did that, my program didnt crash any further. This bunch at Ancestry are clueless about telling people remedies, unless they get so many complaints, that confuses them. They put out patches that screw stuff up or ones that certain people cant even get, try to fix things that are not broke, and give us new stuff, that we clearly tell them we dont like. Give it a try, what the heck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Knight</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/family-tree-maker-2009-minor-update/#comment-38361</link>
		<dc:creator>Tony Knight</dc:creator>
		<pubDate>Sat, 16 May 2009 11:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1189#comment-38361</guid>
		<description>Michael #78 is correct.

Irritating things like gedcoms downloaded fron Ancestry being rejected because they are not version 5.5 or later, but edit the gedcom line in a text editor and its fine.</description>
		<content:encoded><![CDATA[<p>Michael #78 is correct.</p>
<p>Irritating things like gedcoms downloaded fron Ancestry being rejected because they are not version 5.5 or later, but edit the gedcom line in a text editor and its fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/family-tree-maker-2009-minor-update/#comment-38359</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Fri, 15 May 2009 21:52:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1189#comment-38359</guid>
		<description>FTM 2009 crashes regularly when I am simply entering data such as birth, death, etc.  Using the number of people who complain about problems as an indication of application robustness is misleading. Most people don&#039;t bother to report problems until they become totally frustrated. You no doubt have far more unhappy campers than you are aware of. Good luck with your fixes. 

Michael</description>
		<content:encoded><![CDATA[<p>FTM 2009 crashes regularly when I am simply entering data such as birth, death, etc.  Using the number of people who complain about problems as an indication of application robustness is misleading. Most people don&#8217;t bother to report problems until they become totally frustrated. You no doubt have far more unhappy campers than you are aware of. Good luck with your fixes. </p>
<p>Michael</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michelle Pfister</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/family-tree-maker-2009-minor-update/#comment-38345</link>
		<dc:creator>Michelle Pfister</dc:creator>
		<pubDate>Thu, 14 May 2009 23:33:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1189#comment-38345</guid>
		<description>Kenneth #76,

The things you are used to doing in Version 16 are also available in Version 2009. Select the &quot;Publish&quot; Workspace, click on Genealogy Reports, and select &quot;Ahnentafel Report&quot; or one of the other reports.

You can also do custom reports by selecting &quot;Person Reports&quot; and then choosing &quot;Custom Report.&quot;</description>
		<content:encoded><![CDATA[<p>Kenneth #76,</p>
<p>The things you are used to doing in Version 16 are also available in Version 2009. Select the &#8220;Publish&#8221; Workspace, click on Genealogy Reports, and select &#8220;Ahnentafel Report&#8221; or one of the other reports.</p>
<p>You can also do custom reports by selecting &#8220;Person Reports&#8221; and then choosing &#8220;Custom Report.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
