Shape.CellExists property (Visio)

Determines whether a particular ShapeSheet cell exists in the scope of the search. Read-only.


expression. CellExists( _localeSpecificCellName_ , _fExistsLocally_ )

expression A variable that represents a Shape object.


Name Required/Optional Data type Description
localeSpecificCellName Required String The local or universal name of the ShapeSheet cell for which you want to search.
fExistsLocally Required Integer The scope of the search.

Return value



The localeSpecificCellName argument can specify a cell name in either local or universal syntax. To search for a cell by section, row, and column index, use the CellsSRCExists property.

The fExistsLocally argument specifies the scope of the search.

  • If fExistsLocally is non-zero (True), the CellExists property value is True only if the object contains the cell locally; if the cell is inherited, the CellExists property value is False.

  • If fExistsLocally is zero (False), the CellExists property value is True if the object either contains or inherits the cell.

For a list of cell index values, view the Visio type library for the members of class VisCellIndices.


Beginning with Microsoft Visio 2000, you can use both local and universal names to refer to Visio shapes, masters, documents, pages, rows, add-ons, cells, hyperlinks, styles, fonts, master shortcuts, UI objects, and layers. When a user names a shape, for example, the user is specifying a local name. Beginning with Microsoft Office Visio 2003, the ShapeSheet spreadsheet displays only universal names in cell formulas and values. (In prior versions, universal names were not visible in the user interface.)

As a developer, you can use universal names in a program when you don't want to change a name each time a solution is localized. Use the CellExists property to determine if a cell exists by passing either the cell's local name or its universal name. Use the CellExistsU property to determine if a cell exists by passing the cell's universal name.

Support and feedback

Have questions or feedback about Office VBA or this documentation? Please see Office VBA support and feedback for guidance about the ways you can receive support and provide feedback.