<?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: Why policies are made</title>
	<atom:link href="http://rickschummer.com/blog2/2005/10/why-policies-are-made/feed/" rel="self" type="application/rss+xml" />
	<link>http://rickschummer.com/blog2/2005/10/why-policies-are-made/</link>
	<description>Shedding some light on topics of software development, Visual FoxPro, saving our planet, paying it forward, and anything else I find important enough to share.</description>
	<lastBuildDate>Sun, 13 Jan 2019 18:50:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>By: Paul Mrozowski</title>
		<link>http://rickschummer.com/blog2/2005/10/why-policies-are-made/comment-page-1/#comment-1073</link>
		<dc:creator>Paul Mrozowski</dc:creator>
		<pubDate>Fri, 07 Oct 2005 19:23:41 +0000</pubDate>
		<guid isPermaLink="false">http://rickschummer.com/blog2/2005/10/why-policies-are-made/#comment-1073</guid>
		<description>Take a look in the event log; it will usually have an entry there telling you which component it thinks is messed up. If it&#039;s just the class ID you&#039;ll have to search the registry for the program ID, but it will at least point you in the right direction.&lt;br /&gt;&lt;br /&gt;-Paul</description>
		<content:encoded><![CDATA[<p>Take a look in the event log; it will usually have an entry there telling you which component it thinks is messed up. If it&#8217;s just the class ID you&#8217;ll have to search the registry for the program ID, but it will at least point you in the right direction.</p>
<p>-Paul</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Schummer</title>
		<link>http://rickschummer.com/blog2/2005/10/why-policies-are-made/comment-page-1/#comment-1074</link>
		<dc:creator>Rick Schummer</dc:creator>
		<pubDate>Fri, 07 Oct 2005 14:24:41 +0000</pubDate>
		<guid isPermaLink="false">http://rickschummer.com/blog2/2005/10/why-policies-are-made/#comment-1074</guid>
		<description>Malcolm,&lt;br /&gt;&lt;br /&gt;VFP has been using the same setup probably since VFP 6. I don&#039;t think the root cause it the Windows Installer, rather something else destroying or changing a file belonging to or shared with VFP. In fact, VFP and Windows Installer are doing exactly what they are designed to do when something or someone monkeys around with the files.&lt;br /&gt;&lt;br /&gt;My curiosity is the what.</description>
		<content:encoded><![CDATA[<p>Malcolm,</p>
<p>VFP has been using the same setup probably since VFP 6. I don&#8217;t think the root cause it the Windows Installer, rather something else destroying or changing a file belonging to or shared with VFP. In fact, VFP and Windows Installer are doing exactly what they are designed to do when something or someone monkeys around with the files.</p>
<p>My curiosity is the what.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Malcolm Greene</title>
		<link>http://rickschummer.com/blog2/2005/10/why-policies-are-made/comment-page-1/#comment-1075</link>
		<dc:creator>Malcolm Greene</dc:creator>
		<pubDate>Fri, 07 Oct 2005 13:10:17 +0000</pubDate>
		<guid isPermaLink="false">http://rickschummer.com/blog2/2005/10/why-policies-are-made/#comment-1075</guid>
		<description>Rick,&lt;br /&gt;&lt;br /&gt;I recently had the exact same thing happen with the VFP 9 setup trying to run again every time I started VFP. I&#039;ve never had this happen with any of the previous releases of VFP so I believe the root cause of this behavior is VFP&#039;s use of the DREADED Windows Installer technology trying to self-repair the VFP 9 setup when certain configuration details change on your workstation.&lt;br /&gt;&lt;br /&gt;As you point out, the way to repair this is to re-run the VFP setup.&lt;br /&gt;&lt;br /&gt;In addition to remembering to bring setup CD&#039;s with me, I&#039;ve also begun archiving copies of important CD&#039;s (Office, VS Studio, VFP, etc) on my hard drive ... just in case.&lt;br /&gt;&lt;br /&gt;Good luck with your presentations at SWFox!&lt;br /&gt;&lt;br /&gt;Malcolm</description>
		<content:encoded><![CDATA[<p>Rick,</p>
<p>I recently had the exact same thing happen with the VFP 9 setup trying to run again every time I started VFP. I&#8217;ve never had this happen with any of the previous releases of VFP so I believe the root cause of this behavior is VFP&#8217;s use of the DREADED Windows Installer technology trying to self-repair the VFP 9 setup when certain configuration details change on your workstation.</p>
<p>As you point out, the way to repair this is to re-run the VFP setup.</p>
<p>In addition to remembering to bring setup CD&#8217;s with me, I&#8217;ve also begun archiving copies of important CD&#8217;s (Office, VS Studio, VFP, etc) on my hard drive &#8230; just in case.</p>
<p>Good luck with your presentations at SWFox!</p>
<p>Malcolm</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://rickschummer.com/blog2/2005/10/why-policies-are-made/comment-page-1/#comment-1076</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 07 Oct 2005 12:04:12 +0000</pubDate>
		<guid isPermaLink="false">http://rickschummer.com/blog2/2005/10/why-policies-are-made/#comment-1076</guid>
		<description>How hard is it to fire yourself? Put on a wig, look at yourself in the mirror, and in your best Donald Trump imitation say, &quot;You&#039;re fired&quot;.</description>
		<content:encoded><![CDATA[<p>How hard is it to fire yourself? Put on a wig, look at yourself in the mirror, and in your best Donald Trump imitation say, &#8220;You&#8217;re fired&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
