FIX: Windows Internet Explorer 7 does not display a "Save As" dialog box when a script that uses the ExecCommand function together with the SaveAs command runs on a Windows XP-based computer and on a Windows Server 2003-based computer

Consider the following scenario:

• You use Windows Internet Explorer 7 on a Microsoft Windows XP-based computer or on a Microsoft Windows Server 2003-based computer.
• You develop a script that uses the ExecCommand function together with the SaveAs command.
• You set the second parameter in the ExecCommand function to the true value.
  
  Note After you set the second parameter in the ExecCommand function to the true value, you expect Internet Explorer 7 to display a Save As dialog box when you run the script.

In this scenario, Internet Explorer 7 may not display the Save As dialog box when you run the script on the computer.

This problem occurs if you set the third parameter in the ExecCommand function to a file that is not the text file type. The text file type includes .txt files, .html files, and .htm files. For example, you set the third parameter in the ExecCommand function to an .xls file by using the following code. Note This problem does not occur on a Windows Vista-based computer.

This problem occurs because of a limitation in the ExecCommand function. When you run the script that uses the ExecCommand function together with the SaveAs command, the script can only save a file that is the text file type.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows XP Service Pack 2 (SP2) installed.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows XP with SP2, 32-bit version

Hotfix information for Microsoft Windows Server 2003

This problem also occurs on a Microsoft Windows Server 2003-based computer. However, the hotfixes for Windows Server 2003 are all private builds.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 2 (SP2) or Windows Server 2003 Service Pack 1 (SP1) installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 with SP2, x86-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

This hotfix installer adds the following registry values:

• [HKEY_CLASSES_ROOT\.doc] “PerceivedType”=”document”
• [HKEY_CLASSES_ROOT\.dot] “PerceivedType”=”document”
• [HKEY_CLASSES_ROOT\.xls] “PerceivedType”=”document”
• [HKEY_CLASSES_ROOT\.xlt] “PerceivedType”=”document”
• [HKEY_CLASSES_ROOT\.ppt] “PerceivedType”=”document”
• [HKEY_CLASSES_ROOT\.pot] “PerceivedType”=”document”

These registry values are required for this hotfix to take effect.

After you apply this hotfix, the script that uses the ExecCommand function together with the SaveAs command can save more types of files. For example, the script can save the following types of files:

• A .doc file
• A .dot file
• An .xls file
• An .xlt file
• A .ppt file
• A .pot file

For more information, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the SaveAs command, visit the following Microsoft Developer Network (MSDN) Web site: