<?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: The File Cannot Be Accessed</title>
	<atom:link href="http://www.dailydoseofexcel.com/archives/2007/07/31/the-file-cannot-be-accessed/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dailydoseofexcel.com/archives/2007/07/31/the-file-cannot-be-accessed/</link>
	<description>Daily posts of Excel tips…and other stuff</description>
	<lastBuildDate>Thu, 09 Feb 2012 23:42:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Yi-Hsuan Wu</title>
		<link>http://www.dailydoseofexcel.com/archives/2007/07/31/the-file-cannot-be-accessed/#comment-30658</link>
		<dc:creator>Yi-Hsuan Wu</dc:creator>
		<pubDate>Wed, 13 Feb 2008 13:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1704#comment-30658</guid>
		<description>&lt;p&gt;I had the exact same error message except of course the name of the file showed in the message was different. I tried to find the macro.add file but couldn&#039;t locate in the folder. Later, I found out that in my case, it was a bad link in the icon panel. I use macro quite often, so I pulled an icon out to the panel so I can just click on it. It has been working without any problem. But the error message started to show up. However, I can still access the macro through the drop down manu. I guess I can just recreate an icon for the macro later.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I had the exact same error message except of course the name of the file showed in the message was different. I tried to find the macro.add file but couldn&#8217;t locate in the folder. Later, I found out that in my case, it was a bad link in the icon panel. I use macro quite often, so I pulled an icon out to the panel so I can just click on it. It has been working without any problem. But the error message started to show up. However, I can still access the macro through the drop down manu. I guess I can just recreate an icon for the macro later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Witte</title>
		<link>http://www.dailydoseofexcel.com/archives/2007/07/31/the-file-cannot-be-accessed/#comment-26858</link>
		<dc:creator>Jim Witte</dc:creator>
		<pubDate>Wed, 29 Aug 2007 18:57:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1704#comment-26858</guid>
		<description>&lt;p&gt;I managed to find the cause, at least to my problem: I moved the &#039;Macro.add&#039; alias file (found in [Office X directory]/Office/Startup/Excel), and the problem went away.  The Macro.add file is the only one there in the Excel directory, and the original file doesn&#039;t seem to exist, so I just removed the entire Excel directory, and I don&#039;t get the error anymore.&lt;/p&gt;
&lt;p&gt;  Maybe Excel tries to open the Macro.add file, and reports that it can&#039;t be accessed when the alias doesn&#039;t resolve?  A better solution IMO would be to check to see if the alias resolves first - if it doesn&#039;t, alert the user to the SPECIFIC cause of the error (instead of the generic &#039;this file canot be accessed&#039;  - &quot;Which file!?  I&#039;m not trying to open a file?&quot;), and then either delete the nonfunctional alias file, or recreate whatever the Macro.add file is, and where-ever it originally is.  But, this is MS we&#039;re talking about - user-friendlyness especially in border cases like this (this must not happen all that often) do not exactly seem to be a concern.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I managed to find the cause, at least to my problem: I moved the &#8216;Macro.add&#8217; alias file (found in [Office X directory]/Office/Startup/Excel), and the problem went away.  The Macro.add file is the only one there in the Excel directory, and the original file doesn&#8217;t seem to exist, so I just removed the entire Excel directory, and I don&#8217;t get the error anymore.</p>
<p>  Maybe Excel tries to open the Macro.add file, and reports that it can&#8217;t be accessed when the alias doesn&#8217;t resolve?  A better solution IMO would be to check to see if the alias resolves first &#8211; if it doesn&#8217;t, alert the user to the SPECIFIC cause of the error (instead of the generic &#8216;this file canot be accessed&#8217;  &#8211; &#8220;Which file!?  I&#8217;m not trying to open a file?&#8221;), and then either delete the nonfunctional alias file, or recreate whatever the Macro.add file is, and where-ever it originally is.  But, this is MS we&#8217;re talking about &#8211; user-friendlyness especially in border cases like this (this must not happen all that often) do not exactly seem to be a concern.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Witte</title>
		<link>http://www.dailydoseofexcel.com/archives/2007/07/31/the-file-cannot-be-accessed/#comment-26857</link>
		<dc:creator>Jim Witte</dc:creator>
		<pubDate>Wed, 29 Aug 2007 18:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1704#comment-26857</guid>
		<description>&lt;p&gt;I was getting this on OSX Excel (10.1.5 on MacOSX 10.4.10 Intel), so I tried opening Excel itself (no file), and *still* got the error.  This leads me to think that it&#039;s something about a template file somewhere?  Any ideas where?  I got rid of the original &#039;MS Office ACL [English]&#039;, &#039;Excel Settings (10)&#039;, and &#039;Microsoft Office Settings (10)&#039; files, and the problem still occurs (the second and third files are recreated, but not the &#039;ACL&#039; file).  I then tried renaming the ~/Library/Preferences/Microsoft folder (which was recreated), and the problem *still* happened.&lt;/p&gt;
&lt;p&gt;  Any ideas short of a full reinstall?&lt;/p&gt;
&lt;p&gt;Jim&lt;br&gt;
j(witte)swi(NO SPAM)tte@blooming(trees)ton.(dot)in(diana).us&lt;/p&gt;
&lt;p&gt;(This is a &#039;hairy RFC 2822 Address&#039;..)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I was getting this on OSX Excel (10.1.5 on MacOSX 10.4.10 Intel), so I tried opening Excel itself (no file), and *still* got the error.  This leads me to think that it&#8217;s something about a template file somewhere?  Any ideas where?  I got rid of the original &#8216;MS Office ACL [English]&#8216;, &#8216;Excel Settings (10)&#8217;, and &#8216;Microsoft Office Settings (10)&#8217; files, and the problem still occurs (the second and third files are recreated, but not the &#8216;ACL&#8217; file).  I then tried renaming the ~/Library/Preferences/Microsoft folder (which was recreated), and the problem *still* happened.</p>
<p>  Any ideas short of a full reinstall?</p>
<p>Jim<br />
j(witte)swi(NO SPAM)tte@blooming(trees)ton.(dot)in(diana).us</p>
<p>(This is a &#8216;hairy RFC 2822 Address&#8217;..)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fzz</title>
		<link>http://www.dailydoseofexcel.com/archives/2007/07/31/the-file-cannot-be-accessed/#comment-26123</link>
		<dc:creator>fzz</dc:creator>
		<pubDate>Thu, 02 Aug 2007 06:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1704#comment-26123</guid>
		<description>&lt;p&gt;I&#039;d guess the 218 characters have something to do with mapped drive to UNC paths. Like X: mapped to&lt;/p&gt;
&lt;p&gt;\andnowforsomethingcompletelydifferent&lt;/p&gt;
&lt;p&gt;That is, I&#039;m guessing that Excel and maybe other Office programs either store UNC pathnames or insist on making provision for them.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;d guess the 218 characters have something to do with mapped drive to UNC paths. Like X: mapped to</p>
<p>\andnowforsomethingcompletelydifferent</p>
<p>That is, I&#8217;m guessing that Excel and maybe other Office programs either store UNC pathnames or insist on making provision for them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicholas Hebb</title>
		<link>http://www.dailydoseofexcel.com/archives/2007/07/31/the-file-cannot-be-accessed/#comment-26102</link>
		<dc:creator>Nicholas Hebb</dc:creator>
		<pubDate>Wed, 01 Aug 2007 02:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1704#comment-26102</guid>
		<description>&lt;p&gt;I noticed the same last week when testing whether Unicode characters worked in filenames. I thought it was odd too, but the thing that stood out the most was the last line. I&#039;ve always used a MAX_PATH constant of 260. Why does the error message state 218?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I noticed the same last week when testing whether Unicode characters worked in filenames. I thought it was odd too, but the thing that stood out the most was the last line. I&#8217;ve always used a MAX_PATH constant of 260. Why does the error message state 218?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

