When I use the syntax of this statement he doesn't give me any errors.
But when I look at the result in the local cube file he only took 4 of the
20 calculated members.

If I'm not mistaking when I define all measures in this statement he should
automatically also take all the calculated members?

Anyone any idea's?

Greetz,
Nico

You are correct that when a local cube is created using CREATE GLOBAL CUBE
all the calculated members are normally automatically included. However, if
there is some error in the calculation, the calculated member will not be
included, and there will be no error message explaining why that happened.
That makes it difficult to determine what the problem is. Here are some
suggestions that we use in debugging:

1. Verify that the calculated member appears without error when browsing the
server cube. If it displays an error in the server cube, it may not appear
at all in the local cube.

2. Check to see if you have included all the objects needed for the
calculated member in the local cube - measures, other calculated members,
dimensions, levels, etc.

3. Members are automatically excluded in local cubes if they are not
referenced in the fact table. Some calculated members (especially time
period functions) depend on particular members being present. They may be
there in the source cube, but excluded in the local cube. When you are
verifying that all the objects are needed for the calculation to be valid,
verify this by browsing the local cube itself. Make sure all the required
objects are there.

4. Some calculations may have a specific reference to the cube name. If they
do and a different cube name is used for the local cube, the calculated
member will not appear.

5. There is at least one function (LookupCube) that is not supported in
local cubes.

Tim Peterson
www.localcubetask.com


"verbani" <verbani (AT) discussions (DOT) microsoft.com> wrote