business view - failed to open rowset

[splitthird]

We have a Business View based on a couple of Business Elements that are looking at a data foundation connected to a single Oracle 9i data connection.

We are not sure what caused the problem to start - it may have been adding additional tables to the DF, we made no other changes.

What happens is that when we preview the report in CR10 we get:

"failed to open rowset"

Followed by

"Query Engine Error:'If Tables are already linked then the join type cannot change'"


This problem is affecting all the reports - even those that have been running successfully for some time. A very simple new report created of a BV looking at the same Data Foundation gives the same error.
If we create a new data foundation and Business Elements and Business Views, it all works fine.

Has anyone experienced similar behaviour? Any fixes or suggestions?

thanks in advance

 

[pelajhia]

I have not seen this exact error, but it certainly sounds like the tables you just added are the problem.
Or more specifically the linking.
Is there any possibility that you can 'back-out' the changes, at least temporarily removing those tables and re-add them one at a time to figure out which is the issue?

It sounds like this is a change already in your production system.

 

[cmmrfrds]

Did you follow up and check out the message?
"Query Engine Error:'If Tables are already linked then the join type cannot change'"

This seems to indicate that the data type changed on at least 1 field that is being joined in the query. For example, data type from number to varchar.

 

[AZdesertdog]

Splitthird- Did you ever resolve this problem? I'm having the same issue and have tracked down a white paper on it (cr10_left_outer_join.pdf). I am using a dimensional model with multiple facts and found that whenever I created an outer join, I would get the error in CR. The paper describes a registry change:
-----------------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Crystal Decisions\10.0\Crystal Reports\Database\QueryBuilder\JoinBuilder]

@="OJSyntax"

"SQLServerJoinBuilder"="sqlsrv32"
--------------------------------------------------------
which I have implemented on the server with no effect but what I'm curious about is how can this be in the HKEY_CURRENT_USER hive and work?

Anyone else have any ideas on this? I'm using CR10 CE10 against MSSQL2k. Thanks!