Ofread9.txt --------------------------------------------------------- MICROSOFT OFFICE 2000 SR-1 README FILE February 2000 (c) 2000 Microsoft Corporation. All rights reserved. --------------------------------------------------------- This document provides late breaking or other information that is relevant to Office 2000 SR-1, and is current as of the date above. After that date, you may find more current information and resources on the Office Update Web site, available from the Help menu by clicking Office On The Web. Additional information, including network and administration issues, can be found on the Office Resource Kit Web site at: http://www.microsoft.com/office/ork/ There may be additional updates recommended for your computer that you should apply after installing this software. Please consult the file READMORE.TXT located in the \Support folder on CD1. For further technical information on Office, search Product Support Services' collection of technical information, available on the Support Online Web site at: http://support.microsoft.com/support/ For late breaking information specific to an individual Office 2000 product, see the Readme file for that product. For Word, Excel, Outlook, PowerPoint, Access, and FrontPage, these files are located on CD 1 in PFILES\MSOFFICE\OFFICE. For Publisher and Small Business Tools, the file is located at the root of CD2. For PhotoDraw, the file is located at the root of CD3. After installation, Readme files for Word, Excel, Outlook, PowerPoint, Access, PhotoDraw, and FrontPage are stored in C:\Program Files\Microsoft Office\Office. The file names are: WdRead9.txt (Microsoft Word 2000 SR-1) XlRead9.txt (Microsoft Excel 2000 SR-1) OlRead9.txt (Microsoft Outlook 2000 SR-1) PpRead9.txt (Microsoft PowerPoint 2000 SR-1, included in Microsoft Office 2000 Standard, Professional, and Premium) AcRead9.txt (Microsoft Access 2000 SR-1, included in Microsoft Office 2000 SR-1 Professional and Premium) FpRead9.txt and Fpsread9.txt (Microsoft FrontPage 2000 SR-1, included in Microsoft Office 2000 SR-1 Premium) Readme.hlp (Microsoft Publisher 2000 SR-1 and Microsoft Small Business Tools, both included in Microsoft Office 2000 Small Business, Professional, and Premium) Phd2read.doc (Microsoft PhotoDraw 2000 SR-1, included in Microsoft Office 2000 Premium) ReadOSE.txt (Office Server Extensions) ------------------------ How to Use This Document ------------------------ To view the Readme file on-screen in Windows Notepad, maximize the Notepad window. On the Edit menu, click Word Wrap. To print the Readme file, open it in Notepad or another word processor, and then use the Print command on the File menu. -------- CONTENTS -------- ABOUT THE OFFICE REGISTRATION WIZARD AND YOUR PRIVACY INSTALLING MICROSOFT OFFICE 2000 SR-1 * Minimum System Requirements for Microsoft Office 2000 SR-1 * Installation Notes for Windows 2000 and Windows NT 4.0 * Disable Virus Protection Before Running Setup * Using Punctuation Characters in Folder Names During Setup May Cause Problems * Deploying Office 2000 SR-1 * Installing Office 2000 SR-1 on a Network * Prompt for CD Key When Setting Up Office 2000 SR-1 from Administrative Installation * Unexpected Message During Installation * Installing Office 2000 SR-1 Without Removing the Beta 2 Build * Office 2000 SR-1 Shortcuts on the Programs Menu Vary According to Your Operating System * Office 2000 SR-1 Patch Installation not supported for Windows 2000 Power Users * Windows 2000 and Windows NT4 users installing Office 2000 SR-1 per-user will get error installing HTML Source Editing * Windows 2000 Power Users installing Office2000 SR-1 non-elevated will get error installing Web Scripting * Installing Office 2000 SR-1 to Windows 2000 Directory Names with DBCS characters WORKING WITH MICROSOFT OFFICE 2000 SR-1 * Colors May Not Display Correctly on 256-Color Monitors WORKING WITH MICROSOFT OFFICE WEB COMPONENTS * Editing a Formula in a Cell That Contains a Hyperlink * ASC Worksheet Function Not Supported by the Spreadsheet Component MICROSOFT PHOTOEDITOR * Note about Microsoft PhotoEditor MICROSOFT OFFICE 2000 SR-1 HELP ISSUES * Obtaining Microsoft Office 2000 Proofing Tools ISSUES FOR RIGHT-TO-LEFT LANGUAGE FEATURES * Printing Right-to-Left Languages ISSUES FOR ASIAN LANGUAGE FEATURES * Possible Display Problems When Using Multiple Asian Fonts ISSUES FOR MICROSOFT VISUAL BASIC FOR APPLICATIONS * Assistant Object * Add Method (CommandBars Collection) * AddOfficeServerSubscription Method (Office Web Server) * FindControls Method * Context Property (CommandBar Object) * Chart Workspace Object Model (Office Web Components) * SelectionChange Event (Office Web Components) * GetValue Method (Office Web Components) * HTMLData Property (Office Web Components) * KeyChar Property (Office Web Components) * RecordsetLabel Property (Office Web Components) * Value Property (Office Web Components) * Default Language for Visual Basic Editor and Microsoft Script Editor * New Properties (VBA) * Use F3 to Find Next Text Occurrence in the Code Window * Using Digital Certificates in Office 2000 applications SCRIPTING, HTML, AND OTHER PROGRAMMING ISSUES * System Event Notification System * HTML Reference Documentation * Internet Explorer Versions and Editing HTML * "Topic Not Found" Topic (Microsoft Script Editor) ________________________________________________________ ABOUT THE OFFICE REGISTRATION WIZARD AND YOUR PRIVACY Microsoft asks that you register and provide information so that we may verify you as a registered user and provide customized benefits and services. The information that you provide will be securely stored by Microsoft and will be protected from disclosure to third parties without your consent. If you select the option "Receive Microsoft Offers" during registration, Microsoft will send you information about products and services. If you do not want to receive this information, do not select the "Receive Microsoft Offers" option. If you select the option "Receive Non-Microsoft Offers" during registration, Microsoft will carefully select other companies to send you information through postal mail. If you do not want us to do this, do not select the "Receive Non-Microsoft Offers" option. In no case will we provide e-mail addresses or phone numbers to third parties. To ensure that the information that you provide to Microsoft through the Registration Wizard is correct, you can review and update this information by calling the Customer Service Center nearest you during normal business hours. A customer service representative can provide you with the information that we originally received from you. They can also change the information to reflect any corrections or changes you would like to make. The Office Registration Wizard Customer Service Center phone numbers are listed below. Please contact the center nearest you. Australia: 61 2 9870 2131 Brazil: 55 11 822 5764 Hong Kong SAR, PRC: 852 2904 2198 New Zealand: 64 9 357 5576 People's Republic of China: 755 340 9237 Europe: 44 0870 6060439 United States: 716 871 2919 If you believe that Microsoft has not adhered to these privacy principles, please notify us by postal mail at the following address: Microsoft Attn: Office 2000 Registration Wizard Program One Microsoft Way Redmond, Washington 98052-6399 We will use commercially reasonable efforts to promptly determine and correct the problem. ________________________________________________________ INSTALLING MICROSOFT OFFICE 2000 SR-1 Minimum System Requirements for Microsoft Office 2000 SR-1 --------------------------------------------------------- For information about Microsoft Office 2000 SR-1 installation requirements see the Office Resource Kit Web site at: http://www.microsoft.com/office/ork/ Installation Notes for Windows 2000 and Windows NT 4.0 --------------------------------------------------------- To install Office 2000 SR-1 on Windows 2000 or on Windows NT 4.0, you must run Setup with elevated privileges. Elevated privileges give an installation program administrator rights to install software into system areas. To run the installation with elevated privileges, you can use one of the following methods: * Log on to the user’s computer as an administrator before running the installation program. * Advertise the Windows Installer package. When the user first runs the application, the Windows Installer completes the installation under administrator privileges. * Use Windows system policies to allow all Windows Installer packages to install with elevated privileges. * Use Systems Management Server and run the Package Command Manager as a service on the user's computer so that it runs with administrator privileges. * Use Windows 2000 App Deployment to assign or publish Office to the user. * You can also install Office 2000 as a Power User on Windows 2000 without elevated privileges. For more information about installing Office-related software with elevated privileges, see Installing Office with Elevated Privileges on Windows NT 4.0 in the Office 2000 Resource Kit. Disable Virus Protection Before Running Setup --------------------------------------------------------- Some virus protection programs, such as VSafe.com and Norton AntiVirus AutoProtect, can interfere with the Microsoft Office 2000 Setup program. If you use a virus protection program on your computer, disable it before running Setup. (Don't forget to re-enable the virus protection program after Setup is complete.) Using Punctuation Characters in Folder Names During Setup May Cause Problems --------------------------------------------------------- Do not use a comma (,), single quotation mark ('), or exclamation point (!) in the name of the folder where you install Microsoft Office 2000. It is recommended that you use the default folder or use only letters and numbers in folder names. Deploying Office 2000 SR1 --------------------------------------------------------- If you are deploying Office 2000 SR-1 in a corporation or other large organization, be sure to visit the Office Resource Kit web site () for the latest tools and information to help you plan your SR1 deployment. Installing Office 2000 SR-1 on a Network --------------------------------------------------------- >>>To create an administrative installation point for Office 2000 SR-1: 1. Create a share on a network server for the administrative installation point. The network share must have at least 550 megabytes (MB) of available disk space. 2. On a computer running Microsoft Windows 95 or 98 or Microsoft Windows NT (including Windows 2000) and that has write access to the share, connect to the server share. 3. On the Start menu, click Run, and then click Browse. 4. On Office Disc 1 in the CD-ROM drive, select Setup.exe and click Open. 5. On the command line following Setup.exe, type /A DATA1.MSI and click OK. For example: e:\setup.exe /A DATA1.MSI 6. When prompted by Setup, enter the organization name that you want to define for all users who install Office from this location. 7. When prompted for the installation location, enter the server and share you created. For additional information about network and administration issues, see the Office Resource Kit Web site at: http://www.microsoft.com/office/ork/ Prompt for CD Key When Setting Up Office 2000 SR-1 from Administrative Installation --------------------------------------------------------- When you set up Office 2000 SR-1 on your computer from an administrative installation on a server, you might be prompted for a CD Key. This will occur if the system administrator who created the administrative installation did not enter the CD Key. To solve this problem, ask the system administrator to create a new administrative installation and enter the CD Key in the first dialog box. Once this is done, you will not be prompted for the CD Key when you run Setup from this new administrative installation. Unexpected Message During Installation --------------------------------------------------------- If you get an unexpected message during Office setup, and you get the same message when you try setup again, you can create a log file that will be useful to Microsoft Product Support Services in troubleshooting the problem. Once you create the file, you will need to call Microsoft Product Support Services. >>>To create the log file: 1. Click the Start button on the taskbar, and then click Run. 2. In the Open box, type: \SETUP.EXE /L*V C:\VERBOSELOG.TXT where is the location of Setup.exe. For example, if you are installing from a CD-ROM drive, the text you would type might look like: D:\SETUP.EXE /L*V C:\VERBOSELOG.TXT 3. Click OK. Setup will start again and a log file called Verboselog.txt will be created at the root of your C: drive. Installing Office 2000 SR-1 Without Removing the Beta 2 Build --------------------------------------------------------- When starting any of the Office 2000 SR-1 programs, you might receive the following message: Required registry information is missing and this application cannot run. Please rerun Setup to correct this problem. Or, after a few seconds, the program might quit. You might experience either of the above if you installed Office 2000 without removing the Beta 2 build (2221b) of Office 2000. >>>To remove the Beta 2 build: 1. Click the Start button on the taskbar, point to Settings, and click Control Panel. 2. Double-click the Add/Remove Programs icon. 3. In the list of installed programs, click Microsoft Office 2000 Premium Edition. (This is the Beta 2 version of Office 2000.) In the list, there will also be Microsoft Office 2000 Premium. (This is the released version of Office 2000.) 4. Click Add/Remove. 5. Click Remove Office. 6. Click Yes to the prompt confirming that you want to remove. Office 2000 SR-1 Shortcuts on the Programs Menu Vary According to Your Operating System --------------------------------------------------------- The Office 2000 SR-1 shortcuts on the Programs menu might have the following problems: 1. They do not self-repair the programs. This problem occurs because your operating system does not support Windows Installer shortcuts. Only the following versions of Microsoft Windows support these shortcuts: * Windows 98 * Windows 95 with Internet Explorer 4.01, Service Pack 1, and Active Desktop installed * Microsoft Windows NT version 4 with Internet Explorer 4.01, Service Pack 1, and Active Desktop installed Note: If you install Internet Explorer 5 on a computer that has either Windows 95 or Windows NT version 4 and that has Internet Explorer 4.01, Service Pack 1, and Active Desktop installed, it will still support Windows Installer shortcuts. 2. They do not install the programs on first use. This problem occurs because Installed On First Use is not an option for the Office programs in the Selecting Features dialog box during setup. Installed On First Use is not an option because your operating system does not support Windows Installer shortcuts. The operating systems listed under 1. support Windows Installer shortcuts. 3. They do not display a path on the Shortcut tab of the Properties dialog box for the shortcut. This indicates that the shortcut is a Windows Installer shortcut. Windows Installer shortcuts do not directly reference the path of the shortcut target. Instead, they contain a token that the Windows Installer resolves to the path of the shortcut target. The operating systems listed under 1. support Windows Installer shortcuts. Office 2000 SR-1 Patch Installation Not Supported for Windows 2000 Power Users --------------------------------------------------------- Windows 2000 Power Users (on NTFS) attempting to install the Microsoft Office 2000 SR-1 patch directly to their Microsoft Office 2000 installs will get a fatal error that requires rollback. To solve this problem, Windows 2000 Power Users must either install the full SR product from CD, or ask the system administrator to create an SR-1 patched administrative installation image of Microsoft Office 2000, and then install from the source. System administrators can prevent this problem by setting the DisablePatch Windows Installer machine policy, thus blocking users from launching Darwin patches of any product. Windows 2000 and Windows NT4 Users Installing Office 2000 SR-1 Per-User Will Get Error Installing HTML Source Editing -------------------------------------------------------------- Windows 2000 and Windows NT4 users doing a per-user installation of the Office 2000 SR-1 product (i.e. using the AlwaysInstallElevated Windows Installer policy or Win2000 app deployment) will get an error - "Microsoft Development Environment: "Unexpected critical error: can't start program." The message can be dismissed and setup will finish successfully. The effect of dismissing this error and continuing with setup is that the Microsoft Script Editor menu bar will be absent, and Microsoft Script Editor will crash if the toolbar is customized. This error can be prevented by not installing HTML Source editing during initial setup. Windows 2000 Power Users Installing Office 2000 SR-1 Non-Elevated Will Get Error Installing Web Scripting --------------------------------------------------------- Windows 2000 Power Users doing a non-elevated installation of Office 2000 SR-1 product will get an error - "Machine Debug manager: The service could not be uninstalled" when installing the Web Scripting feature. The message can be dismissed and setup will continue. Installing Office 2000 SR-1 to Windows 2000 Directory Names with DBCS characters --------------------------------------------------------- There is a known issue when Office 2000 or Office 2000 SR-1 is installed to US Windows 2000 directory in which the directory name contains characters that are not part of the default code page, specifically Windows 2000 directory names with double-byte characters. Double-byte character sets are typically used in East Asian languages. In certain specific conditions, applications can render incorrect characters or, in extreme instances, the application may hang and current data in the open file could be lost. The conditions are: 1) operating system is US version of Windows 2000; 2) user installs Office 2000 or Office 2000 SR-1 to a directory other than the default directory (i.e., other than C:\Program Files\Microsoft Office); 3) the name of the non-default directory contains double-byte characters in the directory name. There is no current workaround. Recommend reinstalling Office to the default directory. _________________________________________________________ WORKING WITH MICROSOFT OFFICE 2000 SR-1 Colors May Not Display Correctly on 256-Color Monitors --------------------------------------------------------- After you view pop-up windows in Help topics, colors for some elements may no longer display correctly on 256-color monitors. For example, the following elements may appear differently on the screen after you view pop-up windows: * Bitmaps * Pictures embedded in files * Office Assistant * Hyperlinks To fix the display problem, change the color palette for your monitor. >>>To change the color palette: 1. Click Start on the Windows taskbar, point to Settings, and then click Control Panel. 2. Double-click the Display icon. 3. On the Settings tab, select an option other than 256 colors. Microsoft recommends that you choose more than 256 colors, if such an option is available. _________________________________________________________ MICROSOFT OFFICE WEB COMPONENTS ASC Worksheet Function Not Supported by the Spreadsheet Component --------------------------------------------------------- The Help topic "Microsoft Excel worksheet functions not available in Web spreadsheet" does not list the ASC worksheet function, but this function is not available in spreadsheets published on the Web. If you publish a worksheet that contains the ASC function, the function is replaced with its resultant value. Editing a Formula in a Cell That Contains a Hyperlink --------------------------------------------------------- The Help topic "Change a formula in a spreadsheet" incorrectly states that if a cell you want to edit contains a hyperlink, you should click a cell next to that cell, use an arrow key to select the cell you want to edit, and then click the cell once. Clicking the cell once will take you to the page that the hyperlink links to. Instead, once you have used an arrow key to select the cell, press F2 to begin editing. ________________________________________________________ NOTE ABOUT MICROSOFT PHOTOEDITOR Microsoft PhotoEditor is a minor auxiliary application that does not meet the requirements of the Windows 2000 Logo compliant program. Core Microsoft Office applications do not depend on this application for their functionality. _________________________________________________________ MICROSOFT OFFICE 2000 SR-1 HELP ISSUES Obtaining Microsoft Office 2000 Proofing Tools --------------------------------------------------------- Microsoft Office 2000 Proofing Tools is an add-in package for Office 2000 SR-1 that contains all the language tools Microsoft makes for more than 30 languages. It can be obtained from a licensed reseller. The part and SKU numbers listed in Help are incorrect. For more information on obtaining Office 2000 Proofing Tools, see http://www.microsoft.com/office/ _________________________________________________________ ISSUES FOR RIGHT-TO-LEFT LANGUAGE FEATURES Printing Right-to-Left Languages --------------------------------------------------------- Certain printers will require updated printer drivers. Please contact your printer manufacturer if you encounter problems printing. _________________________________________________________ ISSUES FOR ASIAN LANGUAGE FEATURES Possible Display Problems When Using Multiple Asian Fonts --------------------------------------------------------- If you install multiple Asian fonts on non-Asian versions of the Microsoft Windows NT version 4.0 operating system, you might experience display problems, such as very large text, blank text, or very large blank areas occurring in Outlook or in Windows NT. This is a known problem in Windows NT version 4.0 Service Pack 4 that will be fixed in an upcoming Service Pack release for Windows NT version 4.0. ________________________________________________________ ISSUES FOR MICROSOFT VISUAL BASIC FOR APPLICATIONS Assistant Object --------------------------------------------------------- The default Assistant is Clippit, not Rocky as stated in the documentation. Add Method (CommandBars Collection) --------------------------------------------------------- The Temporary argument is ignored in Microsoft Word and Microsoft Outlook. You must manually remove any temporary items added to the CommandBars collection before quitting the application. AddOfficeServerSubscription Method (Office Web Server) --------------------------------------------------------- The MailTo argument of the AddOfficeServerSubscription method is required, not optional as stated in the documentation. FindControls Method --------------------------------------------------------- In the syntax for this method, the keyword should be FindControls, not FindControl as stated in the documentation. Context Property (CommandBar Object) --------------------------------------------------------- In Microsoft Word, the property is read-only and returns the full name (and disk path) of the template associated with the document containing the CommandBar object. In all other Microsoft Office programs, the property returns an empty string and is otherwise unsupported. Chart Workspace Object Model (Office Web Components) --------------------------------------------------------- The diagram for the Chart Workspace object model is incorrect. The WCPlotArea, WCScaling, and WCSeriesCollection objects and all their associated objects should appear under the WCCharts object, not the ChartSpace object as shown in the documentation. Also, the WCCharts object should also contain a WCTitle object. SelectionChange Event (Office Web Components) --------------------------------------------------------- In the SelectionChange event handler for the Spreadsheet component, all properties of the SpreadsheetEventInfo object are invalid for this event with the exception of the Range property. GetValue Method (Office Web Components) --------------------------------------------------------- The Dimension argument can also be either chErrorBarPlusValues or chErrorBarMinusValues for returning values for custom WCErrorBars objects. HTMLData Property (Office Web Components) --------------------------------------------------------- This property is read/write for Spreadsheet objects and read-only for Range objects. KeyChar Property (Office Web Components) --------------------------------------------------------- The KeyChar property returns an empty string for the KeyDown and KeyUp events. RecordsetLabel Property (Office Web Components) --------------------------------------------------------- The RecordsetLabel property of the RecordNavigationControl object is parsed for specific information to use when displaying the label. For example, the tags |0, |1, and |2 are replaced with record numbers when displayed. If the RecordsetLabel property equals the string "Categories |0 of |2;Categories |0-|1 of |2", a label for a banded page might read "Categories 1-5 of 8", and a label for an unbanded page might read "Categories 1 of 8". Value Property (Office Web Components) --------------------------------------------------------- The Remarks section for the Value property states that if the specified range contains more than one cell, this property returns an array containing the values for all the cells. This is incorrect: The property only returns the value of the active cell in the range. Default Language for Visual Basic Editor and Microsoft Script Editor --------------------------------------------------------- The Visual Basic Editor and Microsoft Script Editor default to English if the current system code page does not support the user interface language. New Properties (VBA) --------------------------------------------------------- The following are new properties that apply to class modules in standalone projects: * Instancing Property Sets a value that specifies whether you can create instances of a public class outside a project, and if so, how they will behave. Not available at run time. Settings The Instancing property has these settings: Setting Description ------- ----------- 1 Private (default). Other applications are not allowed access to type library information about the class and cannot create instances of it. Private objects are only for use within your component. The Instancing property default varies depending on the project type. Private is the default only for class modules in standalone projects. 2 PublicNotCreatable. Other applications can use objects of this class only if your component creates the objects first. Other applications cannot use the CreateObject function or the New operator to create objects from the class. * Name Property Returns the name used in code to identify a class. Read-only at run time. Syntax object.Name The object placeholder represents an object expression that evaluates to a class. Remarks An object's Name property must start with a letter and can be a maximum of 40 characters long. It can include numbers and underline (_) characters but can't include punctuation or spaces. Although the Name property setting can be a keyword, property name, or the name of another object, this can create conflicts in your code. Use F3 to Find Next Text Occurrence in the Code Window --------------------------------------------------------- Press F3 to find the next occurrence of previously specified search text in the code window, not SHIFT+F4 as stated in the documentation. Using Digital Certificates in Office 2000 SR-1 applications --------------------------------------------------------- The Visual Basic Programmer's Guide contains a topic "What Are Digital Certificates?" that describes the process used to digitally sign both documents and software. It is important to note that Office 2000 applications provide only the ability to sign VBA projects contained within documents. Office 2000 applications don't provide the ability to sign documents themselves to ensure that text and other contents (other than macros) haven't been altered. However, Microsoft Outlook does provide the ability to digitally sign and encrypt the contents of messages. For more information about signing and encrypting messages in Outlook, search the Microsoft Outlook Help index for "security." ________________________________________________________ SCRIPTING, HTML, AND OTHER PROGRAMMING ISSUES System Event Notification System --------------------------------------------------------- For programmers writing to the System Event Notification System (SENS) and the IEventSubscription and IEventSystem interfaces, please see the documentation for these interfaces at MSDN Online (http://msdn.microsoft.com/) or a version of the Platform SDK later than that which shipped with the April MSDN. HTML Reference Documentation --------------------------------------------------------- The latest HTML, DHTML, and CSS documentation is available online from MSDN Online at http://msdn.microsoft.com/ Internet Explorer Versions and Editing HTML --------------------------------------------------------- Selection works differently in Microsoft Script Editor for sited elements depending on what version of Internet Explorer you have installed. A sited element is any element that has a height or width, such as BUTTON. With Internet Explorer 4.01, selection for sited elements works as follows: * The first click on an element allows you to edit the text within the element. * The second click on an element selects the element. * Double-clicking an element selects the text block within the element. With Internet Explorer 5.0, selection for sited elements works as follows: * The first click on an element selects the element. * The second click on an element allows you to edit the text within the element. * Double-clicking the element brings up the source code for the element. Note: Selection for tables in Internet Explorer 5.0 is the same as it was in Internet Explorer 4.01. Also, Internet Explorer 5.0 preserves white space better than Internet Explorer 4.01 when switching between views in the editor. "Topic Not Found" Topic (Microsoft Script Editor) ------------------------------------------------- You do not need the MSDN Library or MSDN Library CD to view Help topics for Microsoft Script Editor. If you encounter the "Topic not found" topic, try one of the following: * Reinstall Microsoft Script Editor from the Microsoft Office setup. * Insert the Microsoft Office CD into the CD-ROM drive.