Hi again,

I posted this message 2 weeks ago, and got no reply, so submit it again.
Thanks for your feedback.
Note I noticed the same behaviour with PTS9 beta (June CTP)

After installing AS SP4 on server+Pivot Table SP4 on client, I got this bug
:

1- Use cube Budget in Foodmart 2000 sample database
-2 Run this first UPDATE CUBE statement :

UPDATE CUBE [Budget] SET ([Account].[All Account].[Net Income].[Total
Expense].[Lease],[Category].[All Category].[Current Year's
Budget],[Measures].[Amount],[Store].[All
Stores].[Canada].[BC].[Vancouver].[Store 19],[Time].[1998].[Q1])=1000
USE_EQUAL_ALLOCATION

This command performs well. Note the updated cell was Empty before running
command (1000 after)

3- Run this second UPDATE CUBE statement (on the same cell) :

UPDATE CUBE [Budget] SET ([Account].[All Account].[Net Income].[Total
Expense].[Lease],[Category].[All Category].[Current Year's
Budget],[Measures].[Amount],[Store].[All
Stores].[Canada].[BC].[Vancouver].[Store 19],[Time].[1998].[Q1])=2000
USE_WEIGHTED_ALLOCATION

Even if the command execution succeeds, the amount returned for the updated
cell is still 1000 (instead of 2000).
Subsequent calls to UPDATE CUBE on this cell give the same result (new
amount is ignored)
If I use 'USE_EQUAL_ALLOCATION' in the second statement, it will work.

I've reproduced this on client PCs running Pivot Table SP4
There is no problem on client PCs running Pivot Table SP3a

Is this a known bug. I so, how can I correct it ?

Thanks for you help

Michel CARADEC