VB Functions in Excel

[Guest]

My users have requested some special functions added to their Excel
spreadsheets. I've added a module to the spreadsheet and written 6 functions
to handle the user's requirements.

The code ran fine yesterday. After closing the spreadsheet and reopening
it, the value of the functions is appearing as #NAME?. The VB code is still
there as it was yesterday, but the debugging functionality doesn't seem to
work. When you go to the cell with the function and press F2 to Edit and
press enter, the VB editor does not fire off the breakpoints.

I've tried to recompile the VB code, but the Compile option from the Debug
pull down menu option, but it's greyed out.

I will be sending this spreadsheet out to my users for them to copy data
from another spreadsheet.

Thank you, in advance, for any help you all may be able to provide.

Regards,
James W. Hamersly, Jr.
(e-mail address removed)

 

[Ron Rosenfeld]

My users have requested some special functions added to their Excel
spreadsheets. I've added a module to the spreadsheet and written 6 functions
to handle the user's requirements.

The code ran fine yesterday. After closing the spreadsheet and reopening
it, the value of the functions is appearing as #NAME?. The VB code is still
there as it was yesterday, but the debugging functionality doesn't seem to
work. When you go to the cell with the function and press F2 to Edit and
press enter, the VB editor does not fire off the breakpoints.

I've tried to recompile the VB code, but the Compile option from the Debug
pull down menu option, but it's greyed out.

I will be sending this spreadsheet out to my users for them to copy data
from another spreadsheet.

Thank you, in advance, for any help you all may be able to provide.

Regards,
James W. Hamersly, Jr.
(e-mail address removed)

Press the Fx key next to the formula bar and see if your UDF names are
unchanged. Sometimes, when there is ambiguity in the names (i.e. multiple
modules with the same function name) Excel renames the functions to include
enough of a path to make the name unambiguous. In which case, using the
original, shortened form will give a NAME error.


--ron