Hi all,

In a calculated measure, I use the SetToArray MDX-function to pass all descendants of a certain Geography level to an external function
This external function then parses the content of the array, and returns a string representing a set
This string is converted into a set again by the SetToStr MDX-function

When using this calculated measure, I notice a serious increase in the virtual memory used by the client app. (be it the MDX Sample Application, Excel or any other)
This virtual memory only gets released when the client app. is closed, each call further increases the VM

This also happens when I replace the external function by a function that does "nothing", so I think it has nothing to do with the way I programmed the external function :-)

When I run the External Function in the Visual Basic EDI with a breakpoint on the function call, the increase in virtual memory occurs BEFORE I step into the function

So I have the impression the SetToArray function itself is responsible for the increase in VM

Is this a known issue

Is there anything I can do to avoid this (beside of "not using SetToArray")

Thanks for any help