Hi,

I'm using Windows Server 2003 SP1 with Analysis Services 2000 SP3.
When I run the following simple VB Script :

set objCommand=CreateObject("ADODB.Command")
objCommand.ActiveConnection="provider=msolap; Datasource=localhost; Initial Catalog=FoodMart 2000; Connect Timeout=5"

const strMember="[Sales].[Time].[My Member]"

on error resume next

for nIdx=1 to 1000
objCommand.CommandText="CREATE MEMBER " & strMember & " as 'null'"
objCommand.Execute
if Err.Number<>0 then
msgbox Err.Description & " " & cstr(nIdx)
exit for
end if

objCommand.CommandText="DROP MEMBER " & strMember
objCommand.Execute
next

set objCommand=nothing

I get an error at the 760th step.
In BOL (Specifications and Limits), it is said :
"Calculated members in a parent dimension member in session context" can't exceed 759.

What I miss here is that each time, I run a DROP MEMBER command before creating my member again.
Is this behaviour by design, or is it unexpected ?

Thanks for your help

Michel CARADEC

This is known limitation of Analysis Services 2000. It is fixed in Yukon.

--
==============================*=================== =
Mosha Pasumansky - http://www.mosha.com/msolap
Analysis Services blog at http://www.sqljunkies.com/WebL*og/mosha
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==============================*=================== =
"Michel CARADEC" <mcaradec (AT) nospam_openexecutive (DOT) com> wrote

Hi,

I'm using Windows Server 2003 SP1 with Analysis Services 2000 SP3.
When I run the following simple VB Script :

set objCommand=CreateObject("ADODB.Command")
objCommand.ActiveConnection="provider=msolap; Datasource=localhost; Initial
Catalog=FoodMart 2000; Connect Timeout=5"

const strMember="[Sales].[Time].[My Member]"

on error resume next

for nIdx=1 to 1000
objCommand.CommandText="CREATE MEMBER " & strMember & " as 'null'"
objCommand.Execute
if Err.Number<>0 then
msgbox Err.Description & " " & cstr(nIdx)
exit for
end if

objCommand.CommandText="DROP MEMBER " & strMember
objCommand.Execute
next

set objCommand=nothing

I get an error at the 760th step.
In BOL (Specifications and Limits), it is said :
"Calculated members in a parent dimension member in session context"
can't exceed 759.

What I miss here is that each time, I run a DROP MEMBER command before
creating my member again.
Is this behaviour by design, or is it unexpected ?

Thanks for your help

Michel CARADEC