Hello all. I have successfully set up real-time olap on MS Analysis
Service 2000 SP4 using SQL Server 2000 SP3 as the data source (all on
Windows 2003 SP1). Both the cube (fact table) and dimensions refresh
automatically when data is added to the relational data source. I am
using OWC as the front-end component.

Here's the problem: If a user is browsing the cube via OWC and a new
record is added to the fact table, further browsing via OWC is not
possible as all cells turn to #VALUE or #ERR, until they hit refresh on
OWC. This does not happen when dimension members are added or changed.
Of course, this is completely unacceptable as records are added to the
fact table on average every 15 seconds or so, while leaves my users
refreshing the OWC pivot control constantely, unable to actually *use*
it to do any appreciable work. Note that this also happens with the
built-in "Browse Cube" functionality in MMC. I have changed the Auto
Sync Period to 0, which removed the #err but still disallows further
browsing.

I have read the white paper at
http://msdn.microsoft.com/library/de...l-timeolap.asp
and it did discuss the issues with syncing clients, but did not say it
was as impossible as I am seeing. In fact, their example of frequency
of change @ 10 seconds is about what I have.

Sorry for the long message! Any suggestions? Has anyone used OWC with
real-time cubes and had success?