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 a Microsoft Certified Partner or Microsoft Advisory Services. For more information, visit these Microsoft Web sites:
Microsoft Certified Partners -
https://partner.microsoft.com/global/30000104Microsoft Advisory Services -
http://support.microsoft.com/gp/advisoryserviceFor more information about the support options that are available and about how to contact Microsoft, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
To work around this behavior, substitute
Application.Caller for the
ActiveCell property wherever it is used in the custom function. For example, if the custom function is the following
Function Test()
Application.Volatile
' Returns the cell one column to the left of the active cell. Note
' that the active cell is not necessarily the cell that is calling
' the function.
Test = ActiveCell.Offset(0, -1).Value
End Function
you should change it to the following:
Function Test()
Application.Volatile
' Returns the cell one column to the left of the cell that is
' actually calling the function.
Test = Application.Caller.Offset(0, -1).Value
End Function
When you do this, the function correctly uses the cell that is calling the
function instead of using the currently active cell.