Page 323 of 972« First...102030...321322323324325...330340350...Last »

XL2000: Error Message: Cannot Place Chart on a Hidden Sheet

You receive the following error message:

Cannot place chart on a hidden sheet.

NOTE: Microsoft Office 2000 has built-in functionality that permits you to get more information about difficult-to-troubleshoot alerts or error messages. If you want to enable this functionality for this and other error messages in Microsoft Office 2000, please download the Microsoft Office 2000 Customizable Alerts file from the Microsoft Office Update Web site at the following address:
NOTE: If you reached this article by clicking the Web Info button in an error message, you already have Customizable Alerts enabled.

Microsoft requires more information about your specific situation to
determine why you got this error message.

Contact Microsoft Product Support Services

Please contact Microsoft Product Support Services by using the contact information provided on the support options page at:

When you contact support, please refer to article ID Q234682.

Article ID: 234682 – Last Review: November 2, 2013 – Revision: 5.0


Applies to
  • Microsoft Excel 2000 Standard Edition
kbnosurvey kbarchive kbdownload kbprb KB234682

Read More:
XL2000: Error Message: Cannot Place Chart on a Hidden Sheet

MS08-014: Description of the security update for Excel 2000: March 11, 2008

Microsoft has released security bulletin MS08-014. The security bulletin contains all the relevant information about the security update. This information includes file manifest information and deployment options. To view the complete security bulletin, visit one of the following Microsoft Web sites:

How to obtain help and support for this security update

Help installing updates:
Support for Microsoft Update

(http://support.microsoft.com/ph/6527)

Security solutions for IT professionals:
TechNet Security Troubleshooting and Support

(http://technet.microsoft.com/security/bb980617.aspx)

Help protect your computer that is running Windows from viruses and malware:
Virus Solution and Security Center

(http://support.microsoft.com/contactus/cu_sc_virsec_master)

Local support according to your country:
International Support

(http://support.microsoft.com/common/international.aspx)

Prerequisites

You must have Microsoft Office 2000 Service Pack 3 (SP3) installed to apply this security update.

For more information about how to obtain Office 2000 SP3, click the following article number to view the article in the Microsoft Knowledge Base:

276367

(http://support.microsoft.com/kb/276367/
)

How to obtain the latest service pack for Office 2000

Removal information

To remove this security update, use Add or Remove Programs in Control Panel.

Article ID: 946979 – Last Review: November 2, 2013 – Revision: 3.0


Applies to
  • Microsoft Excel 2000 Standard Edition
kbnosurvey kbarchive kboffice2000sp3fix kbexpertisebeginner kbqfe kbsecurity kbsecbulletin kbsecvulnerability kbbug kbfix KB946979

See the original post:
MS08-014: Description of the security update for Excel 2000: March 11, 2008

Error message when you approve an invoice in Microsoft Dynamics AX 3.0 with Service Pack 6 installed: "Cost Value must be positive upon receipt in Inventory"

When you approve an invoice for a purchase order in Microsoft Dynamics AX 3.0 with Service Pack 6 installed, you receive the following error message:

Cost Value must be positive upon receipt in Inventory.

This problem occurs if the following conditions are true:

  • The purchase order is a project order.
  • The Post financial inventory check box is selected in the Inventory model groups dialog box.

Hotfix information

A supported hotfix is now available from Microsoft. The hotfix corrects the problem that is described in this article. Apply the hotfix only to systems that are experiencing this specific problem.

To resolve this problem immediately, contact your Microsoft Dynamics partner or Technical Support for Microsoft Dynamics and related products to obtain the hotfix. If you have access to online assisted support you can log on to the Microsoft Dynamics site and create a new support request. To do this, visit the following Microsoft Web site:

You can also contact Technical Support for Microsoft Dynamics and related products by telephone. To do this, visit the following Microsoft Web site:

Partners

CustomersIn special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.

This hotfix is not scheduled to be included with a Microsoft Dynamics AX 3.0 service pack.
If you are a customer and if you do not have a Premier Support Agreement with Microsoft, you must contact your partner to obtain this hotfix.

Installation information

If you have customizations for one or more of the methods or the tables that are affected by this hotfix, you must follow these steps:

  1. Review the changes that are documented in the .xpo file.
  2. Apply these changes in a test environment before you apply the hotfix in a production environment.

For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

893082

(http://support.microsoft.com/kb/893082/
)

How to install a Microsoft Dynamics AX hotfix

Prerequisites

No prerequisites are required.

Restart requirement

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

Objects that are affected

This hotfix affects the following objects:

  • Data DictionaryTablesInventTrans:checkCostValue
  • ClassesInventUpd_FinancialupdateFinancialReceipt
  • ClassesInventMov_PurchupdateLedgerFinancial
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.

THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Article ID: 952902 – Last Review: November 2, 2013 – Revision: 4.0


Applies to
  • Microsoft Dynamics AX 3.0
  • Project
kbnosurvey kbarchive kberrmsg kbexpertiseadvanced kbexpertiseinter kbqfe kbmbsmigrate kbhotfixserver KB952902

See the article here:
Error message when you approve an invoice in Microsoft Dynamics AX 3.0 with Service Pack 6 installed: "Cost Value must be positive upon receipt in Inventory"

All the quantities that are available do not appear when you create or update a bill of material and then run the BOM function "Max. report as Finished" in Microsoft Dynamics AX 3.0

You create or update a bill of material and then run the BOM function Max. report as Finished in Microsoft Dynamics AX 3.0. In this situation, all the quantities that are available from all the warehouses do not appear.
This problem occurs when the warehouse is not specified on the bill of material.

When a warehouse is not specified, you expect all the quantities that are available from all the warehouses to appear.

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem.

To resolve this problem immediately, contact Microsoft Business Solutions Technical Support to obtain the hotfix. You can log on to the Microsoft Business Solutions Support site and create a new support request. To do this, visit the following Microsoft Web site:

You can also contact Microsoft Business Solutions Technical Support by telephone at (888) 477-7877.

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Business Solutions Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.
If you are a customer and if you do not have a Premier Support Agreement with Microsoft, you must contact your partner to obtain this hotfix.

Installation information

If you have customizations to one or more of the methods or the tables that are affected by this hotfix, you must follow these steps:

  1. Review the change in the code in the updateBOMConsumption method of ClassesBOMReportFinish_Max.

    Existing code

    (...)
        if (BOMparmReportFinish.overrideDimension)
            tmpBOM.dimension = BOMparmReportFinish.dimension;
    
        onHandI = conFind(onHandCon,#onHandId);
    
        inventOnhand = InventOnhand::newItemDim(
            tmpBOM.itemId,
            tmpBOM.inventDim(),
            childInventDimParm,
            true);
        tmpBOM.inventOnHand = inventOnhand.availPhysical();
    (...)
    

    Replacement code

    (...)
        if (BOMparmReportFinish.overrideDimension)
            tmpBOM.dimension = BOMparmReportFinish.dimension;
    
        onHandI = conFind(onHandCon,#onHandId);
    
        childInventDimParm.initFromInventDim(tmpBOM.inventDim());
    
        inventOnhand = InventOnhand::newItemDim(
            tmpBOM.itemId,
            tmpBOM.inventDim(),
            childInventDimParm,
            true);
        tmpBOM.inventOnHand = inventOnhand.availPhysical();
    (...)
    

  2. Apply these changes in a test environment before you apply the hotfix in a production environment.

For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

893082

(http://support.microsoft.com/kb/893082/
)

How to install a Microsoft Dynamics AX hotfix

Prerequisites

You must have Service Pack 4 for Microsoft Dynamics AX 3.0 installed to apply this hotfix.

Removal information

You cannot remove this hotfix.

Restart requirement

If you are prompted to restart the computer, you must restart the computer after you apply this hotfix.

Objects that are affected

This hotfix affects the following object:

  • ClassesBOMReportFinish_Max
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

Article ID: 923219 – Last Review: November 2, 2013 – Revision: 3.0


Applies to
  • Microsoft Dynamics AX 3.0
  • Logistics
kbnosurvey kbarchive kbfix kbqfe kbmbsmigrate KB923219

Read more here:
All the quantities that are available do not appear when you create or update a bill of material and then run the BOM function "Max. report as Finished" in Microsoft Dynamics AX 3.0

The current return cost price is lost when you update the quantity on a sales order line in Sales Order in Microsoft Dynamics AX 3.0

When you update the quantity on a sales order line in Sales Order in Microsoft Dynamics AX 3.0, the return cost price is lost. If the sales order line is invoiced, the inventory is returned at zero cost.

Additionally, you may receive an error message that resembles the following:

Return lot ID or return cost price is missing for returned item

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem.

To resolve this problem immediately, contact Microsoft Business Solutions Technical Support to obtain the hotfix. You can log on to the Microsoft Business Solutions Support site and create a new support request. To do this, visit the following Microsoft Web site:

You can also contact Microsoft Business Solutions Technical Support by telephone at (888) 477-7877.

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Business Solutions Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.
If you are a customer and if you do not have a Premier Support Agreement with Microsoft, you must contact your partner to obtain this hotfix.

Installation information

If you have customizations to one or more of the methods or the tables that are affected by this hotfix, you must follow these steps:

  1. Review the changes that are documented in the .xpo file.
  2. Apply these changes in a test environment before you apply the hotfix in a production environment.

For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

893082

(http://support.microsoft.com/kb/893082/
)

How to install a Microsoft Dynamics AX Hotfix

Prerequisites

You must have Service Pack 4 for Microsoft Dynamics AX 3.0 installed to apply this hotfix.

Removal information

You cannot remove this hotfix.

Restart requirement

If you are prompted to restart the computer, you must restart the computer after you apply this hotfix.

Objects that are affected

This hotfix affects the following object:

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

Article ID: 922598 – Last Review: November 2, 2013 – Revision: 3.0


Applies to
  • Microsoft Dynamics AX 3.0
  • Trade
kbnosurvey kbarchive kberrmsg kbaxapta30presp6fix kbqfe kbmbsmigrate kbHotfixServer KB922598

Follow this link:
The current return cost price is lost when you update the quantity on a sales order line in Sales Order in Microsoft Dynamics AX 3.0

The exchange rate is doubled when you reverse the exchange adjustment for an account in Accounts Payable in Microsoft Dynamics AX 3.0

When you reverse the exchange adjustment for an account in Accounts Payable in Microsoft Dynamics AX 3.0, the exchange rate is doubled. This problem occurs when you split the original invoice transaction by using the Transaction Reorganizing function.
This problem occurs because reversing the exchange adjustment calculates the exchange adjustment from the original invoice transaction amount. Instead, reversing the exchange adjustment should calculate the amount that is included in the open transaction editing form.

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem.

To resolve this problem immediately, contact Microsoft Business Solutions Technical Support to obtain the hotfix. You can log on to the Microsoft Business Solutions Support site and create a new support request. To do this, visit the following Microsoft Web site:
-

You can also contact Microsoft Business Solutions Technical Support by telephone at (888) 477-7877.

Note
In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Business Solutions Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.
If you are a customer and if you do not have a Premier Support Agreement with Microsoft, you must contact your partner to obtain this hotfix.

Installation information

If you have customizations to one or more of the methods or the tables that are affected by this hotfix, you must follow these steps:

  1. Review the changes that are documented in the .xpo file.
  2. Apply these changes in a test environment before you apply the hotfix in a production environment.

For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

893082

(http://support.microsoft.com/kb/893082/
)

How to install a Microsoft Dynamics AX Hotfix

Prerequisites

You must have Microsoft Dynamics AX 3.0 Service Pack 5 installed to apply this hotfix.

Removal information

You cannot remove this hotfix.

Restart requirement

If you are prompted to restart the computer, you must restart the computer after you apply this hotfix.

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.

Collapse this tableExpand this table

File name File version File size Date Time Platform
17913.exe Not Applicable 37,672 06-Jul-2006 03:15 x86
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

Article ID: 922605 – Last Review: November 2, 2013 – Revision: 3.0


Applies to
  • Microsoft Dynamics AX 3.0
  • Financials
kbnosurvey kbarchive kbaxapta30presp6fix kbqfe kbmbsmigrate kbHotfixServer KB922605

Visit link:
The exchange rate is doubled when you reverse the exchange adjustment for an account in Accounts Payable in Microsoft Dynamics AX 3.0

ACC2000: Lookup Wizard Error: You Already Have a Field Named…

This article was previously published under Q197111

This article has been archived. It is offered “as is” and will no longer be updated.

Moderate: Requires basic macro, coding, and interoperability skills.
When you use the Lookup Wizard to create a field that looks up or lists
values from a table, and the first field name in the lookup table has the
same field name as the Lookup field that you are creating, you may receive
the error message:

You already have a field named <'fieldname'>

if you click to select the Hide Key Column check box when you create the field.

Make sure that the Hide Key Column check box is not selected when you see the screen that asks How wide would you like the columns in your lookup column?

To create a Lookup field, follow these steps:

  1. Start Microsoft Access and open the sample database Northwind.mdb.
  2. Create a new table in Design view, and add a Text field named Field1.
    Save the table as Table1, and click Yes when prompted if you want to
    create a primary key now.
  3. Create a second table in Design view, and add a Text field named ID.
  4. Add a second field named Test. In the Data Type column, click the down arrow, and then click LookUp Wizard.
  5. When the Lookup Wizard starts, select the default option I want the lookup column to look up the values in a table or query, and then click Next.
  6. On the second screen of the Lookup Wizard, under Which table or query should provide the values for your lookup column?, select Table1, and then click Next.
  7. On the third screen of the Lookup Wizard, move both fields under
    Available Fields to the Selected Fields box by clicking the >> button, and then click Next.
  8. On the fourth screen of the Lookup Wizard, which asks How wide would you like the columns in your lookup column?, make sure that the Hide Key Column check box is not selected, and then click Next.
  9. On the fifth screen of the Lookup Wizard, select Field1 in the
    Available Fields box, and then click Next.
  10. On the sixth screen of the Lookup Wizard, which asks What label would you like for your lookup column?, note that the suggested label for the lookup column is Test. Click Finish, and then click Yes to the message that says that The table must be saved before relationships can be created. Save now?
  11. In the Save As dialog box, click OK to save the table with the default name Table2, and then click No when you see the message There is no primary key defined.

    Note that the table is saved with the Lookup field without an error.

Steps to Reproduce Behavior

  1. Repeat steps 1 through 7 in the “Resolution” section.
  2. On the screen that asks How wide would you like the columns in your lookup column, make sure the Hide Key Column check box is selected, and then click Next.
  3. When you see the screen that asks What label would you like for your lookup column?, note that the suggested label for the lookup column is Test. Click Finish, and then click Yes to the message The table must be saved before relationships can be created. Save now?
  4. In the Save As dialog box, click OK to save the table with the default name Table2, and then click No when you see the message There is no primary key defined. Note that the field name has now been changed from Test to ID, and you receive the error message:

    You already have a field named “ID.”

For more information about the Lookup Wizard, click Microsoft Access Help on the Help menu, type create a field that looks up or lists values intables in the Office Assistant or the Answer Wizard, and then click Search to view the topic.

Article ID: 197111 – Last Review: November 2, 2013 – Revision: 3.0


Applies to
  • Microsoft Access 2000 Standard Edition
kbnosurvey kbarchive kbprb KB197111

Visit link:
ACC2000: Lookup Wizard Error: You Already Have a Field Named…

XL2002: Text Spanning Multiple Cells Truncated When Saved as HTML

If you publish a worksheet as a Web page, and the worksheet contains text that spans multiple cells, the text does not appear properly when you open the Web page in your browser. For example, if you type the following text in cell A1

The quick brown fox jumps over the lazy dog.

and then publish the worksheet, the text in your browser appears truncated or is wrapped within cell A1.

This does not affect how the text looks when you open the file in Microsoft Excel.

Unlike Excel, Hypertext Markup Language (HTML) does not allow text to spill across multiple cells in a table. When you publish an HTML file that contains text that spills across multiple cells, Excel attempts to merge all of the cells in which the text spills together, so that they display correctly in the browser. However, Excel can only do this if the following conditions are true:

  • The text that spills across multiple cells is left-aligned or general-aligned in the source cell.

    -and-

  • The cells into which the text spills are empty.

    -and-

  • The cells into which the text spills contain formatting identical to the source cell.

If Excel is unable to merge cells together when saving the HTML file, the spilled text may not appear correctly in a browser. Some browsers interpret HTML differently, so that you may see different results depending on which browser you use to view the workbook. The following table shows how the text may appear in different browsers:

   If you have this browser          You may see this behavior
   -----------------------------------------------------------------------

   Microsoft Internet Explorer 5     Text is cropped
   Microsoft Internet Explorer 4     Text is either cropped or wrapped
                                     to a new line.
   Netscape Navigator 4              Text may be cropped, wrapped to a
                                     new line, or is not displayed.
   Microsoft Internet Explorer 3     Text is wrapped to a new line.
   Netscape Navigator 3              Text is wrapped to a new line. Row and
                                     column heights and widths may not be
                                     maintained.
				

Note that in Excel, if you open an HTML workbook containing spilled text, the spilled text is displayed correctly.

To work around this problem, use either of the following methods.

Method 1: Merge the Cells into Which the Text Spills

  1. In Excel, select all the cells into which the text spills (including the source cell for the text).
  2. On the Format menu, click Cells.
  3. Click the Alignment tab.
  4. Under Text control, click Merge cells.
  5. Click OK.

Method 2: AutoFit the Column Containing the Spilled Text

  1. In Excel, select the column containing the source cell for the text.
  2. On the Format menu, point to Column, and then click AutoFit Selection.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Article ID: 291212 – Last Review: November 2, 2013 – Revision: 2.0


Applies to
  • Microsoft Excel 2002 Standard Edition
kbnosurvey kbarchive kbbug kbconversion kbpending KB291212

Read more here:
XL2002: Text Spanning Multiple Cells Truncated When Saved as HTML

XL2001: Excel Hangs When You Attempt to Copy Worksheet in Same Workbook

If you attempt to copy a sheet, Microsoft Excel may stop responding (hang), and you must click Force Quit (press COMMAND+OPTION+ESC), or restart. This may result in the loss of any unsaved data.
This problem occurs when the following conditions are true:
  • A worksheet is copied more than once into its originating workbook, by using any method, including Microsoft Visual Basic for Applications (VBA).

    -and-

  • The workbook contains, or has previously contained, a VBA module.

NOTE: The problem may occur the first time that you copy a sheet in an existing workbook, if there are copies of the same sheet in the workbook from previous use.

To resolve this problem, download and install the Microsoft Office 2001 Service Release 1 file.

Note The Microsoft Office 2001 Service Release 1 (SR-1) update is no longer available as a separate download. To obtain Microsoft Office 2001 Service Release 1 (SR-1), download and install the Microsoft Office 2001 Combined Update 9.0.5. To do so, visit the following Microsoft Web site:

To temporarily work around this problem, use any of the following methods.

Method 1: Copy a File Only Once

Create only one copy of a sheet. For additional copies, copy the copy, and continue to copy any new copies only once.

Method 2: Copy a File to Another Workbook

Copy a file to another workbook and then move it back into the original workbook.

Method 3: Copy Worksheets Only in Files Without VBA Modules

Copy sheets only in workbooks that have no modules. Use code in a separate workbook.

NOTE: This method may only work if the file is newly created in Excel 2001. Removing existing modules may not solve the problem, but moving the sheets to a new workbook may allow you to copy a sheet multiple times within the new workbook.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was corrected in Microsoft Office 2001 for Mac Service Release 1.
For more information about how to copy sheets, follow these steps:
  1. On the Help menu, click Contents and Index, click Index, and then click C.
  2. Scroll down until you locate copy, and then click the arrow to the left to view a list of topics under the general topic.
  3. Click Move or copy sheets.

If you cannot find the information that you want, ask the Office Assistant.

For additional information about the Office 2001 Service Release, click the article number below
to view the article in the Microsoft Knowledge Base:

294949

(http://support.microsoft.com/kb/294949/EN-US/
)

OFF2001: Readme for Microsoft Office 2001 for Mac Service Release 1 (SR-1)

Or, visit the Microsoft MacTopia Web site (http://www.microsoft.com/mac

(http://www.microsoft.com/mac)

) for any additional updates.

Article ID: 286266 – Last Review: November 2, 2013 – Revision: 5.0


Applies to
  • Microsoft Excel 2001 for Mac
kbnosurvey kbarchive kbbug kbdtacode kbpending KB286266

View article:
XL2001: Excel Hangs When You Attempt to Copy Worksheet in Same Workbook

XL2001: Total Row in List Shifts After Adding Data in Earlier Version of Excel

In Microsoft Excel 2001 for Mac, when you open a workbook that contains a list that was created with List Manager, the position of the Total Row may be shifted incorrectly.

The word “Total” and the SUBTOTAL formula are incorrectly placed in the New Record Row. (The row below the New Record Row typically contains these items, and also contains the Total Row controls, which are seen when you click these cells.) In addition, if you click outside the List Object, the text and formula in the New Record Row may disappear.

This problem occurs when you do the following:

  1. Create a list with List Manager in Excel 2001.
  2. Open the Excel 2001 workbook in one of the following earlier versions of Excel:
    • Microsoft Excel 98 Macintosh Edition
    • Microsoft Excel 97 for Windows
    • Microsoft Excel 2000

  3. In the earlier version of Excel, add data to the list, and then save the workbook.
  4. Reopen the workbook in Excel 2001.

This problem occurs because the List Manager is a new feature in Excel 2001. Earlier versions of Excel may cause unexpected behavior or data loss when used to edit files that contain list objects.

To resolve this problem, download and install the Microsoft Office 2001 Service Release 1 file. To do so, visit the following Microsoft Web site:
To temporarily work around this problem, before you save the file, click a cell outside the list, so that the List Object is not selected.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was corrected in Microsoft Office 2001 for Mac Service Release 1.
This problem only occurs if you save the worksheet when the list is active and the New Record Row is present.
For additional information about the Office 2001 Service Release, click the article number below
to view the article in the Microsoft Knowledge Base:

294949

(http://support.microsoft.com/kb/294949/EN-US/
)

OFF2001: Readme for Microsoft Office 2001 for Mac Service Release 1 (SR-1)

Or, visit the Microsoft MacTopia Web site (http://www.microsoft.com/mac

(http://www.microsoft.com/mac)

) for any additional updates.

Article ID: 298482 – Last Review: November 2, 2013 – Revision: 3.0


Applies to
  • Microsoft Excel 2001 for Mac
kbnosurvey kbarchive kbbug kbfix KB298482

Excerpt from:
XL2001: Total Row in List Shifts After Adding Data in Earlier Version of Excel

Page 323 of 972« First...102030...321322323324325...330340350...Last »

Recent Comments

    Archives

    Categories