ODBC Unstable when using Multiple Connections

[BeeBear2]

Hi,

Using CR Ver 11.5

I dont think this is a Crystal Reports issue, but I'm just trying to rule it out before going back to my helpdesk (as they have no CR knowledge, and will just blame Crystal settings).

My issue is, I have TWO separate databases, with two separate ODBC Connections, and if I open up one report in Crystal to Database 1 (Ingres Database), and another completely separate report to Database 2 (Oracle Database), then either one or the other connections will drop out and I get a connection error. It is not routinely one database over the other, but I have noticed, that whichever one I open second, has the issue.

At first, if I open both, and run both, its no issue, but if I then leave it for a while before refreshing the data, its like the connection times out, and asks for a username/pwd again.
My helpdesk are also loathe to give out a password too, so it was saved automatically somewhere,

For the last 5 months I've been connection to DB1 with no issues at all and no need for username/pwd, it was only when I requested a second DB connection, that the issues started appearing.

Hoping you guys can point me in the right direction before I go back to the heldesk - they even suggested it was a CMC Console issue, thanks to Google-Help - Had to point out to them that we don't have the CMC products.

Thanks

 

[AndersonCJA]

Hello,

I have run into similar difficulties using different odbc connections. What has worked for me is to use a sub report for the other database connection.
And, create a formula field in both the main report and the sub report and use the formula field to link from the main report to the sub report.

 

[BeeBear2]

Thanks, I'll give that a go.

We are meant to be having the non-Oracle database converted to Oracle by now, but that seems to have stalled because they can't work out how to do it....... SIGH!

 

[AndersonCJA]

I looked at a report this morning to see if I could find other details to share that might help.
I found that the linking is different from what I suggested/remembered.
In my main report, the account number Key field is converted to a string in a formula field. That Formula field is linked to the subreport using the subreports' table.field key link of account number which is already a string. (not another formula field as I had remembered and suggested). Both the main report and the subreport are grouped by the account number.

 

[hilfy]

I also highly suggest that you use a "Native" Oracle connection instead of ODBC. I have found over the years that Crystal's Native Oracle connection is MUCH more stable and faster than using ODBC. Also, the newest version of the Oracle client that you want to use is 11g - something was changed in the 12c client that causes problems for Crystal.

Also, the version of Crystal that you're using (XI r2) is old and has been out of support for a number of years. It was never designed to work on modern operating systems - I think the last one it was verified to work on was XP. So, unless you're using Crystal with some older software, you might want to consider upgrading to the latest version - Crystal 2016. You can download a trial version here:

http://go.sap.com/product/analytics/crystal-reports.html.

-Dell

DecisionFirst Technologies - Seven-time SAP BusinessObjects Solution Partner of the Year

http://www.decisionfirst.com

 

[BeeBear2]

Thanks guys,

I would love to upgrade to the new version, but at this stage I'm having trouble even getting the publishing end of the tool. Baby steps lol