[AngieGirl]

Hi!!!

I have a VB application, a report must be lunch from it, this report has 3 subreports, but the problem is that the main report connects to SQL Server in a Server A and the subreports connect to Sybase System 11 in a Server B, the report works with both connections in the Crystal Report Designer, but when I use the OCX in vb, the report gives me an error "20599 Cannot Open SQL Server" I have other reports without subreports some using the Sybase connection and some others the Sql Server connection and all of them runs perfectly.

So the problem appears in a report with subreports. I have read and implement a lot of suggestions without find a solution.

I need help in this, because I had spent a lot of time looking for a solution without success.

[Rockn]

If other reports can run using the connections to either database then there is obviously a problem with your current report setup. Can you run the sub-reports outside of the main report and get the desired results? If you can get the sub-reports to run separately try your main form minus the sub-reports. Are the parent/child fields linked correctly as well?

[AngieGirl]

Well, I have tried this, I already run my subreports and main report separately and they work fine, there is no problem with the links because in the Crystal Report Designer the report works fine, I thought that the problem could be that the main report is using an ODBC Connection, but the subreports use a direct connection to sybase, I made another report with both connections using ODBC but the problem de persists.

[Rockn]

Is the report designer adding anything extra to the report that after it is saved is messing with the final report? Are the ODBC connections all on your local PC or running at the server with DSN entries? Might want to upgrade MDAC just in case and possibly see if there is an updated ODBC driver for Sybase.