XL2000: Custom Function Returns #VALUE! Error After Running Macro (213679)
The information in this article applies to:
This article was previously published under Q213679 SYMPTOMS
If you call a user-defined (custom) function from a worksheet formula, and
then run a Microsoft Visual Basic for Applications macro, the user-defined
function may return the #VALUE! error.
CAUSE
This problem occurs if all of the following conditions are true:
- You create a custom function, and then call it from a worksheet formula.
-and-
- The custom function uses the Text property for a Range object.
-and-
- You run another Sub procedure (macro) that deletes a row in the worksheet.
RESOLUTION
To resolve this problem, use the Value property instead of the Text property in the custom function.
NOTE: If you must use the Text property, recalculate the formulas in the workbook by pressing CTRL+ALT+F9.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. MORE INFORMATION
You can use the Text property or the Value property with a Range object. The Value property returns the actual underlying cell value, while the Text property returns the formatted value that is displayed in the cell.
REFERENCESFor more information about the Text property, in the Visual Basic Editor, click Microsoft Visual Basic Help on the Help menu, type Text property (Excel) in the Office Assistant or the Answer Wizard, and then click Search to view the topic.
| Modification Type: | Minor | Last Reviewed: | 10/10/2006 |
|---|
| Keywords: | kbbug kbpending kbProgramming KB213679 |
|---|
|