Microsoft Knowledge Base Email Alertz

An application that uses .NET Framework to monitor the event log does not read the descriptions from COM and DCOM sources on a computer that is running Windows Vista or Windows Server 2008

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 200804 - Last Review: September 27, 2001 - Revision: 1.0

FP2000: Importing Files from a Unix Server Will Not Import All Files

This article was previously published under Q200804

For a Microsoft FrontPage 98 version of this article, see 238139  (http://kbalertz.com/Feedback.aspx?kbNumber=238139/EN-US/ ) .
For a Microsoft FrontPage 97 version of this article, see 238138  (http://kbalertz.com/Feedback.aspx?kbNumber=238138/EN-US/ ) .

SYMPTOMS

If you import files with the same name but with different case from a Unix server into a Windows-based server, hyperlinks to at least one of the files will break.

CAUSE

Unix operating systems are case sensitive.

For example: Files called "mypage.htm" and "Mypage.htm" are recognized as different files on the Unix operating system. Because Windows-based operating systems are not case sensitive, these two files are recognized as being the same file.

RESOLUTION

Save the file with lowercase letters from a Web browser. Change the name of the file, and then import it into FrontPage.

APPLIES TO
  • Microsoft FrontPage 2000 Standard Edition
Keywords: 
kbprb KB200804
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate