Hello Everyone,

I have written the core to an OLAP application using DSO and VB6.

I can build my cube and create parent/child dimensions without any difficulty.

When I add the dimension to the cube everything looks right, I can update the
cube, but processing the cube fails with the following message:

Run-time error '-2147221386 (80040076)':

The column prefix 'BSegE_Cube_ProjectEnterpriseText2_Outline' does
not match with a table name or alias name used in the query.;42000;The
column prefix 'BSegE_Cube_ProjectEnterpriseText1_Outline' does not
match with a table name or alias name used in the query.;42000

If I end my DSO application and go to the Analysis Manager, I receive
essentially the same error when I manually select and attempt to process the
cube.

BUT!, if I select and open the cube in the Analysis Manager editor there are
no apparent or indicated errors. If I then save the cube on exiting the
editor (having made no changes of any sort) I can then select and process the
cube with no errors what so ever.

I have spent several hours trying to figure this problem out and would greatly
appreciate any assistance this might be offered. Frankly, this is a knot hole
I would consider paying someone to help me through.

What does this run-time error really mean?

What could the editor be fixing by simply saving the cube?

How do I fix this in my DSO application?

HELP!!!!!

Bob

Bob Segrest, PMP
BSegE LLC
(540) 937-5875
http://www.BSegE.com

Your technique is OK, it is just that AM has done some magic under the
covers that you don't know about. What I typically recommend in a case like
yours is to get a copy of the SQL Server 2000 Resource Kit. On it is a
utility called the Metadata Scripter. It outputs VB code which recreates
objects using DSO. My guess is that there is some property which is
misformatted,

1) Create the objects using your program.
2) Run the metadata scripter to recreate the dimension / partition in
question -- it generated VBProgA.vbs
3) Run AM to "fix" the situation
4) Run the metadata scripter to see what the objects now look like -- it
generates VBProgB.vbs
5) Do a windiff between VBProgA.vbs and VBProgB.vbs

Like I said, I think you will find that a property has been changed by AM
when it "fixes" the value.

Hope that helps.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Bob Segrest" <Bob.Segrest (AT) BSegE (DOT) com> wrote

Hi Dave,

Thank you very much for the tool pointer. I have downloaded the resource kit
and am running WinDiff now.

Bob

Bob Segrest, PMP
BSegE LLC
(540) 937-5875
http://www.BSegE.com

Bob: How did you download the tool? There is a outstanding post from someone
wanting to know how to get the metadata scripter. Thanks.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Bob Segrest" <Bob.Segrest (AT) BSegE (DOT) com> wrote

Hi Dave,

I was not able to find it on any of the public Microsoft sites. It would
appear that the SQL 2000 materials have been trashed with the SQL 2005
release.

It is available from the MSDN subscribers download site and can be found in
the SQL part of the tree. Unfortunately, you need to be a MSDN subscriber to
get there.

However, in the past the Microsoft telephone support people have been pretty
good about helping people with access to obsolete but support product
downloads. If the person asking is not a MSDN subscriber, I would try this
first.


Bob Segrest, PMP
BSegE LLC
(540) 937-5875
http://www.BSegE.com

Can you post the path for MSDN subscribers?
That would help greatly.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Bob Segrest" <Bob.Segrest (AT) BSegE (DOT) com> wrote