#REF! error with UDF

Hi freeky1 and welcome to ExcelForum,

Your post does not comply with Rule 3 of our Forum RULES. Use code tags around code.

Posting code between [CODE]Please [url=https://www.excelforum.com/login.php]Login or Register [/url] to view this content.[/CODE] tags makes your code much easier to read and copy for testing, it also maintains VBA formatting.

Highlight your code and click the # icon at the top of your post window. More information about these and other tags can be found here

(This thread should receive no further responses until this moderation request is fulfilled, as per Forum Rule 7)


Since this is your first post, I will answer your question. You will get no further replies until you put CODE TAGS around your code in your original question.

Your code works fine for me exactly as written, both in VBA and as a function in a cell. To test your function, put a breakpoint at the start of the function. After you type in the function in the cell, the breakpoint should be activated, and you can single step through the function using the f8 key.

The following may help you now and in the future.

It is a best practice to declare all variables. If you misspell a variable in your code, VBA will silently assume it is a Variant variable and go on executing with no clue to you that you have a bug. Go to the VBA development window, click Tools, Options, and check "Require Variable Declaration." This will insert the following line at the top of all new modules:

Please Login or Register  to view this content.

This option requires all variables to be declared and will give a compiler error for undeclared variables.

Debugger Secrets:
a. Press 'F8' to single step (goes into subroutines and functions).
b. Press SHIFT 'F8' to single step OVER subroutines and functions.
c. Press CTRL 'F8' to stop at the line where the cursor is.
d. 'Left Click' the margin to the left of a line to set (or clear) a BREAKPOINT.
e. Press CTRL 'G' to open the IMMEDIATE WINDOW. 'debug.print' statements send their
output to the IMMEDIATE WINDOW.
f. Select View > Locals to see all variables while debugging.
g. To automatically set a BREAKPOINT at a certain location put in the line:
'Debug.Assert False'
h. To conditionally set a BREAKPOINT at a certain location put in lines similar to:
if i >= 20 and xTV20 > 99.56 then
Debug.Assert False
endif
i. A variable value will be displayed by putting the cursor over the variable name.

Lewis

This is the workbook I am working on.
Thanks

Darn, this value is just a step of many calculations to follow, if it is #ref! then all the functions to follow are #value!. Hopefully someone will figure this out one day.

Originally Posted by MrShorty

So, instead of suggesting renaming the function(s), should I encourage the OP to come join me on the dark side using R1C1 notation regularly?

That worked perfectly,
Great thanks

Originally Posted by MrShorty

So, instead of suggesting renaming the function(s), should I encourage the OP to come join me on the dark side using R1C1 notation regularly?

How do you toggle the R1C1 style on, so instead of A B C I will see C1, C2 etc... ?
Thanks