Comments on: Exposing VBA code through Excel objects

By: excelthoughts

excelthoughts — Wed, 22 Jun 2005 07:14:00 +0000

Stephen,

This is incredibly useful for my work. (I am constantly having Application.Run problems).

I am looking forward to receiving your book in the mail (Professional Excel Development)

Andrew
excelthoughts.com

By: Doug Glancy

Doug Glancy — Wed, 22 Jun 2005 05:32:00 +0000

This post was very informative, and helpful to me in an indirect way. I've been pairing addins with workbooks, but don't want any code in the workbooks (otherwise after reading this post I would have done what Alex suggests above). I was using defined names in the workbooks, but when I read Stephen's comment about their susceptibility to alteration I went in another direction. I'm now using matching VBProject names. So the main application addin checks each workbook that's activated/deactivated to see if it's VBProject name matches that of an addin in the same folder. If they match it creates a menu for the workbook based on code stored in the matching addin.

Anyways, thanks Stephen. BTW, reading your book the other day helped me understand how to return more than one argument from a function (if that's the right way to say it) by passing parameters ByRef. Very cool, my validation code is now much more concise. It's interesting how as I learn new things the code gets shorter. 2 weeks later and there's only a couple of screenfuls...

By: Alex J

Alex J — Wed, 22 Jun 2005 04:17:00 +0000

So could this be done with add-ins (meaning the showname code would be in the add-in and called from a workbook)? Might be a nice way to invoke add-in functions.

By: XL-Dennis

XL-Dennis — Sun, 19 Jun 2005 00:58:00 +0000

Gentlemen – You get things to look so very simple

Thanks!

Kind regards,
Dennis

By: David Hager

David Hager — Sat, 18 Jun 2005 22:17:00 +0000

As always, Iím sure that Stephen is being generous in allowing someone else to point out that this same methodology can also be applied to function procedures .

Place the following simple function in key sheet modules:

Function Mult(a, b)

Mult = a * b

End Function

Then, place this function in a standard module:

Function MultipleFuncResult(m, n)

On Error Resume Next

For Each wks In ThisWorkbook.Worksheets
MultipleFuncResult = _
MultipleFuncResult + wks.Mult(wks.Range(mwks.Range(n))
Next

End Function

Finally, enter =MultipleFuncResult(ìa1î, ìa2î) in a worksheet cell. The cumulative result of the this function will only come from those worksheets that have a Mult function in its sheet module.

Thanks, Stephen!

By: jkpieterse

jkpieterse — Sat, 18 Jun 2005 21:15:00 +0000

Nice catch Stephen, One to remember and use!