? " ... can be usaed in excel ... " ?
but ... but ... but if "it" can be used in Excel, what stops you from using it in most any (other) VBA context?
At the least, if you include the class / library in Excel, you can then call them from any / all VB(A) context.
In general, the confusion arises from not understanding the Excel procedures (calls). When their is a "Range" reference in Excel, it translates "directly" to an aray reference for VB(A).
For a S I M L I S T I C example, if the Excel function needs a range reference or 5 contigious cells in a column / row (e.g. B2:B5) you can call it with an array of five. A reloatively easy example is StdDev. Excel requires a "List" of n[\i] values which may be expressed as a Cell Range (an older version of the Excel Function reference shows the use of 10 VALUES, in a Range (A2:E3). You can call the Excel function from Ms. A. with an array of the 10 values. I occassionally resort to this approach to get some program working, usually sending a ParamArray of the values to the Excel function.
The caveats here are just two (that I know of). First is the need to include the Excel function library as a reference in the application. In your case, I would expect that the library reference could be directly included in Ms. A. The second (and occassionally more onorous issue is that you must have a clear understanding of the expected input and return arguments. This includes knowing the number and type of all arguments. It is possible for either the input or return arguments to include (or BE) a "UDF", so that a specific structure would need to be built to accomodate the function. I have not (at least yet) found any such requirement in my use of any Excel function, but then I have alos not come even close to using all of them in this manner.
MichaelRed