XL2000: #VALUE! Appears When Function Is Recalculated

• Microsoft Excel 2000

SYMPTOMS

In Microsoft Excel, cells that contain formulas that refer to user-defined functions may return a #VALUE! error after you run a Visual Basic for Applications macro or perform any action that causes the worksheet that contains the formulas to be recalculated.

Also, if a Visual Basic subroutine is running when the formulas are recalculated, the subroutine may stop without warning.

CAUSE

These problems may occur if an error occurs in a user-defined function while Excel is recalculating the worksheet.

For an example of this problem, see the "More Information" section later in this article.

WORKAROUND

Microsoft provides programming examples 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. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft Support professionals can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact the Microsoft fee-based consulting line at (800) 936-5200. For more information about the support options available from Microsoft, please see the following page on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

 Function MyFunction(CellRange As Object) As String
     On Error GoTo ErrorHandler                    'error-handling code
     If CellRange.Interior.Pattern = xlNone Then
         MyFunction = "yes"
     Else
         MyFunction = "no"
     End If
     Exit Function                                 'exit if no error.
 ErrorHandler:                                     'error-handling code.
     MyFunction = "error"                          'error-handling code.
 End Function 

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

In Microsoft Excel, if a user-defined function returns an error value, the formula that called the user-defined function and any other formulas that call the same user-defined function may fail to be recalculated properly. When this happens, the formulas may return a #VALUE! error.

Also, if the user-defined function returns an error value, any running Visual Basic subroutine that caused the recalculation to occur may stop. This may cause problems if the subroutine is running unattended.

To see examples of these problems, follow these steps:

1. In Microsoft Excel, create a new workbook.



2. On the Tools menu, point to Macro, and then click Visual Basic Editor. Then, click Module on the Insert menu.



3. Enter the following code into the new module:
   

   
    Function MyFunction(CellRange As Object) As String
    
        'This line will fail when you delete a row from the worksheet.
        If CellRange.Interior.Pattern = xlNone Then
            MyFunction = "yes"
        Else
            MyFunction = "no"
        End If
    End Function
    
    Sub TestDelete()
        Rows(2).Delete             'Deleting a row forces recalculation.
        MsgBox "Delete succeeded."
    End Sub 




4. On the File menu, click Close and Return to Microsoft Excel.



5. Select cells A10:A12 in the worksheet. Type the following formula

   =MyFunction(C10)

   
   and press CTRL+ENTER.
   
   All three cells (A10, A11, A12) display the value "yes."



6. On the Tools menu, point to Macro, and click Macros. Select TestDelete, and then click Run.
   
   Note that the three cells (A9, A10, A11) display the #VALUE! error value. Note also that the message box in the TestDelete subroutine is not displayed.



7. Press CTRL+ALT+F9.

Additional query words: XL2000

Keywords : kbdta xlvbainfo xlformula
Version : WINDOWS:2000
Platform : WINDOWS
Issue type : kbbug