XL97: BottomRightCell/TopLeftCell Incorrect with Merged Cell

Last reviewed: January 9, 1998
Article ID: Q169107
The information in this article applies to:
  • Microsoft Excel 97 for Windows

SYMPTOMS

In Microsoft Excel 97, if you run a Visual Basic for Applications macro that checks the BottomRightCell property or TopLeftCell property of a drawing object, AutoShape, chart, or other object, the address of the cell may appear to be incorrect.

CAUSE

This problem occurs if the BottomRightCell or TopLeftCell returns the address of a merged cell.

WORKAROUND

Microsoft provides examples of Visual Basic for Applications procedures for illustration only, without warranty either expressed or implied, including, but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. The Visual Basic procedures in this article are provided 'as is' and Microsoft does not guarantee that they can be used in all situations. While Microsoft support engineers can help explain the functionality of a particular macro, they will not modify these examples to provide added functionality, nor will they help you construct macros to meet your specific needs. If you have limited programming experience, you may want to consult one of the Microsoft Solution Providers. Solution Providers offer a wide range of fee-based services, including creating custom macros. For more information about Microsoft Solution Providers, call Microsoft Customer Information Service at (800) 426-9400.

If you want to return the address of the merged cell that lies beneath the upper-left corner or the lower-right corner of an object, modify the code so that it checks the address of the upper-leftmost cell of the MergeArea that lies beneath the object. For example, instead of using the following code

   X = ActiveSheet.Shapes(1).TopLeftCell.Address

use this code:

   X = ActiveSheet.Shapes(1).TopLeftCell.MergeArea.Resize(1, 1).Address

The MergeArea property returns the entire range of cells that is merged into a single cell. The Resize method returns the upper-leftmost cell of the MergeArea. The Address property returns the address of the merged cell.

You can use the same process with the BottomRightCell property of objects.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

When you check the BottomRightCell property or the TopLeftCell property of an object in Microsoft Excel 97, the property does not recognize that the worksheet may contain merged cells. As a result, each property returns the address of the cell that would have been under the upper-left or lower- right corner of the object if the cells had not been merged.

To demonstrate this behavior, use the following steps:

  1. In Microsoft Excel 97, create a new workbook.

  2. Select the range of cells B2:F6. On the Formatting toolbar, click Merge And Center.

  3. Using the Rectangle tool on the Drawing toolbar, draw a rectangle that is completely within the merged cell.

  4. On the Tools menu, point to Macro, and then click Visual Basic Editor.

  5. On the View menu, click Immediate Window.

  6. Type the following command

          ?Sheets(1).Shapes(1).BottomRightCell.Address
    

    and press ENTER.

    The Immediate window returns $F$6 even though the rectangle is completely within the merged cell ($B$2).

  7. Type the following command

          ?Sheets(1).Shapes(1).BottomRightCell.MergeArea.Resize(1, 1).Address
    

    and press ENTER.

The Immediate window returns $B$2, the correct address.


Additional query words: XL97
Keywords : xldraw xlformat xlvbahowto xlvbainfo kberrmsg
Version : WINDOWS:97
Platform : WINDOWS
Issue type : kbprb


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 9, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.