Hi -

Anyone else had a problem with excel refusing to see XLL function
calls if /at any time/ the workbook has had a vba module containing
the same function name?

Cells just return #name! - 'saving as' (the usual way to get round
excel cruft like this) doesn't work - the only way (short of XMLifying
the book!) I've found is to dump the xls into a hex editor, and
modify the reference to the function in the xls's shared string table.

(of course, if there are any other symbols sharing the same name as
the function I'm 'renaming', they tend to get renamed too,
inconvenient.....)

(problem seen in excel 2000, a friend verified it in XP...)

Anyone worked round this in a more elegant way? :)

Cheers,

Lee.

Try using Rob Bovey's free code cleaner utility. It exports all the code
modules, then saves the workbook, then imports them back in. This should
clean up the symbols table.

http://www.appspro.com

--
Regards,
Tom Ogilvy

Lee Benfield wrote in message
...
Hi -

Anyone else had a problem with excel refusing to see XLL function
calls if /at any time/ the workbook has had a vba module containing
the same function name?

Cells just return #name! - 'saving as' (the usual way to get round
excel cruft like this) doesn't work - the only way (short of XMLifying
the book!) I've found is to dump the xls into a hex editor, and
modify the reference to the function in the xls's shared string table.

(of course, if there are any other symbols sharing the same name as
the function I'm 'renaming', they tend to get renamed too,
inconvenient.....)

(problem seen in excel 2000, a friend verified it in XP...)

Anyone worked round this in a more elegant way? :)

Cheers,

Lee.