XL97: Custom Function Returns #VALUE! Error After Running Macro (175226)


The information in this article applies to:

  • Microsoft Excel 97 for Windows
This article was previously published under Q175226

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.

STATUS

Microsoft 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.

REFERENCES

For more information about the Text property, click the Office Assistant in the Visual Basic Editor, type "text," click Search, and then click to view "Text Property (Excel 97)."

NOTE: If the Assistant is hidden, click the Office Assistant button on the Standard toolbar. If the Assistant is not able to answer your query, please see the following article in the Microsoft Knowledge Base:

176476 OFF: Office Assistant Not Answering Visual Basic Questions

Modification Type:MinorLast Reviewed:10/11/2006
Keywords:kbbug kbProgramming KB175226
©2004 Microsoft Corporation. All rights reserved.