WorksheetCell.Value
When a formula, array formula, or data table is applied to a cell, the Value property of the WorksheetCell will no longer return the Formula, ArrayFormula, or WorksheetDataTable instance applied to the cell. Now it will return the calculated value of the cell. To get the formula or array formula of the cell, there is a new Formula property which will return the Formula or ArrayFormula instance. If a formula is not applied to the cell, this property will return null. To get the data table of the cell, there is a new AssociatedDataTable property which will return the WorksheetDataTable instance applied to the cell. If the cell is not a cell within a data table, this property will return null.
WorksheetMergedCellsRegion.Value
When a formula is applied to a merged cells region, the Value property of the WorksheetMergedCellsRegion will no longer return the Formula instance applied to the cell. Now it will return the calculated value of the cell. To get the formula of the merged cells region, there is a new Formula property which will return the Formula instance. If a formula is not applied to the merged cells region, this property will return null.
Non Top-Left Cells of Merged Cells Regions
In previous versions of Excel, getting the value of any cell within a merged cells region would return the value of the associated merged cells region. This is actually incorrect and can be verified through the use of formulas (referencing the non top-left cell of a merged cells region in a formula uses a null or zero for the cell’s value). Now null will be returned for any cell associated with a merged cells region except for the top-left cell, which will continue to return the merged cells region’s value. Setting the value of any cell other than the top-left cell will have no action and will not cause an exception. Setting the value of the top-left cell of the merged cells region will set the value of the merged cells region as well.
Removing a Worksheet
Invalid Values to Operators in UltraCalcManager
When using the UltraCalcManager in previous versions, if non-numerical values were passed to operators (such as =“Hello”+5), a #NUM! error would have occurred. This is inconsistent with Excel though. Now they will correctly cause a #VALUE! Error to occur.