Hi DK,
You've just done what it takes (that is, posting your message to the
newsgroup) to make Microsoft aware of the problem.
Your hunch about the file name length could be correct, or there could
be some other cause.
Next, Microsoft will have to analyze the cause of the problem,
prioritize working on a solution, come up with a solution, test the
solution, and then deploy it. Not every bug will be a high enough
priority to cause a fix to be made, but this one sounds like it is
pretty likely to get worked on given that several people have reported it.
The best way to make sure you get updates when they becomes available is
from the menu choose Help > Check For Updates and set it to check daily.
-Jim
--
Jim Gordon
Mac MVP
MVP FAQ
<http://mvp.support.microsoft.com/default.aspx?scid=fh;EN-US;mvpfaqs>
DK wrote:
> I have had the same "Cannot Access Files" problem since moving over to
> Excel 2004 from Excel X. Using Excel 2004, I find that I can move the
> subject file up about 4 levels in my Folder hierarchy and then Excel
> can open the file and save it - but only at that same level or above.
> Any attempt to save the file back into its original nested folder
> location produces the same error message. Is it possible that the
> length of file name is, in fact, the problem?? And, if so, what does
> it take to get MS to act on the bug?<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Cannot access files on Windows Server