Hi, i have this problem (I'm using analisys services 2000) i have a fact table Services with two dimensions Clasifications, and Prices.
The fact table has three dimensions IdServices, IdClasifications and IdPrices, idclasifications and idprices are fk to the tables of Clasifications and Prices.
I wan to count the services so i have measure on the field IdServices wiht count.
The problem is that it doesn't count all the services, all the services with the field idclasification in null are not count.
Is there a way to solve this
Thanks

Null Problem
Abdul Wasie
In my case, i have a unique id field, is the field that i using to count...
My original problem is this:
I have a fk in the fact table to a dimension, this fk can be null, i have other dimensions too, the problem is: in the fact table i have only the rows that this fk field is not null, and i want all the rows... I need all the rows becaues i want to examine the data using the other dimensions too..
Daniel McElhinney
I am in analysis services 2000....
I don't find how to set a measure usage to "Count of rows"..
The solution you gave is fot AS2000
SLMOFLZ
dseifert
Mac Whore
JonathanMA
The idea is simply to identify a candidate key - a set of columns that uniquely identifies each row - and concatinate these columns into a single column value. In the worst case scenario where all columns are independent this could mean concatinating all columns in the table. If this is the case, you'll probably want to go back and add an identity (a.k.a. autoincrement) column to the table to serve as a key. As an example on the SQL Server sysobjects table, you could concatinate the name, id, and xtype columns into a single column using the following query (although this is not necessary for sysobjects since name is already unique and non-nullable):
select
name + '|' + Convert( varchar, id) + '|' + xtype from sysobjectsJCakeC
billwhelop
Ok, now I understand. To have counts for the rows with null FK values included in the cube, you must associate members in the dimension the FK refers to since ever cell must have a co-ordinate in each dimension. The easiest way to do this is to add a new "unknown member" to the dimension table (can be done with a SQL view using a Union) and then replacing null values in the fact table FK column with references to the new "unknown member". The null replacement in the FK column can be done with a SQL expression either in a view or the source column property.
Nchantim