Upgrading from Crystal Reports 8.5 to 11 - ADAPT00538716

Question

I recently upgraded to version 11 and found that most of my reports don&#39;t work due to the fact that I have different join types in a report.  Using the knowledge base, I found the problem had been encountered and assigned <a href="http://technicalsupport.businessobjects.com/KanisaSupportSite/search.do?cmd=displayKC&docType=kc&externalId=c2018884&sliceId=&dialogID=2788854&stateId=1%200%202794021" target="_blank">ADAPT00538716</a>.  There is a workaround which calls for using a stored procedure or command objects.  The only problem is that I have over 500 reports so recreating all of them doesn&#39;t sound very appealing.  I have thought about going back to 8.5 until the bug is fixed, but Business Objects can&#39;t give me a timeline of when if ever this will be fixed.  Has anyone figured another way around this?

Answer 1

Hi todderor,
This is a serious, major issue. Many database projects will need multiple link types per table. Now if CRXI can't handle this, this is a major problem for the applicability of the software. In fact, had I known this I wouldn't have bought the app and I am now seriously considering asking for a rebate and investigating alternatives !
 I don't want to need to do stuff with S.P.'s, views or queries since this is one of the - if not the major - reasons I bought CRXI in the first place, namely to unburden my DBA and empower end-users to browse data w/o having to bother him for details.
 In our project, we have a table "Indicator" that contains a column "Alternative Indicator" that is a reference to the same table (optional reference). The table also joins to - say / sake of argument - a table "Client".
Now, the link between "Indicator" and "Client" is an inner join and it should be, since all Indicators bear reference to a Client.
However, the link between the alias "Alternative Indicator" (for "Indicator") is off course an "OUTER JOIN" since I do not want to limit my report to only those Indicators having an alternative Indicator (there are only few). The link between the aliased "AlternativeIndicator" and the "Client" Table must be inner join again, off course.
NO GO. CRXI error. Product rendered useless.
Please inform your community to the time of delivery for an update for this showstopping, critical error in the apparantly prematurely released software product !
Yours,
Thijs Cobben