A
Avi Perez
Hi
I have a strange behavior in the operation of my app that I was hoping
someone would have solved previously, or at least seen before:
I have an AS2K SP3 server running 2 virtual cubes - identical to each other.
One is the real production version (made some time ago), the other is a
clone I made (but not copied) from scratch today. My OWC app is running on
a WinXP client with IE6 SP2. Running the EXACT same MDX against these cubes,
with the EXACT same connection string (https), on the exact same page with
the exact same scripts, one cube will return data the other won't. The error
states "Failed to get data".
My question is this: is there something structural in OWC that responds
differently to the version of MDAC a cube was created under? That is the
only thing I can think of that is fundamentally different between version 1
and 2. Strangely enough, both cubes work perfectly with other pivot table
apps: Excel, ProClarity and server side ASP queries.
Any thoughts?
Thx
Avi
I have a strange behavior in the operation of my app that I was hoping
someone would have solved previously, or at least seen before:
I have an AS2K SP3 server running 2 virtual cubes - identical to each other.
One is the real production version (made some time ago), the other is a
clone I made (but not copied) from scratch today. My OWC app is running on
a WinXP client with IE6 SP2. Running the EXACT same MDX against these cubes,
with the EXACT same connection string (https), on the exact same page with
the exact same scripts, one cube will return data the other won't. The error
states "Failed to get data".
My question is this: is there something structural in OWC that responds
differently to the version of MDAC a cube was created under? That is the
only thing I can think of that is fundamentally different between version 1
and 2. Strangely enough, both cubes work perfectly with other pivot table
apps: Excel, ProClarity and server side ASP queries.
Any thoughts?
Thx
Avi