ODBC Error when report with subreports executed 1

[maryellc]

Using CR 8.5 Developer version. I have a report with two subreports, and each subreport accesses data from SQL Server database and Ingres Database (ODBC). After entering parameters to run the report, I receive the following messages twice: "ODBC error:" and "Error detected by database dll". The ODBC error has no specifics as to where the error is. If I use the same tables in a separate report, it runs without error. I have a feeling it is either a dll problem or a log on problem with the SQL server database. Can anyone help?

 

[pgtek]

hi
it seam to be a log on problem.
If your prompt twice and you have 2 subreport thats where
the problem reside.
check your login info for your subreport if they are pass.

cheers



pgtek

 

[maryellc]

Thanks for the tip. Just curious - why am I able to run each subreport standalone without error? Both databases have automatic login when I startup and I am not prompted at any point to log in when reports are run off either database.

 

[pgtek]

Hi

if run seperated they will work fine
but when you pass the parameter thru the main
this is where it flinch.
check your link in the main to sub report and your paramter on each main and subreport that they are ok

I work with Ingres in the pass
and it's an obselete database system. computer Associate
are no longer supporting this database.

cheers





pgtek

 

[synapsevampire]

What connectivity are you using to the SQL Server? You should be using the CR supplied ODBC driver, not the MS. You might also try the Convert Database Driver and Verrify Database to make sure everything is properly configured. Since you have differing datasources, don't let iut propagate changes across all databases.

The driver may also be hiccuping due to a difference in data types, otherwise in theory this should work OK.

-k

 

[maryellc]

I'm not sure that the parameters are the problem.

I recently introduced, within both subreports, data from a SQL server database. Both subreports access two tables - one from ingres and one from SQL server. Each database has a different log on and I automatically log in to each database when I sign on. Can Crystal not handle a subreport with two different log on ids, since I can successfully run a standalone report with each database's tables?

 

[maryellc]

the 'verify database' answer was the correct one! When I created the tables in the SQL database, I did so by adding an additional field that was the same data type as the fields I would be linking to in my ingres database. I could run the report with subreports successfully. The day after I ran this report for the first time, the tables had been rebuilt on the SQL server database.

By performing 'verify database', Crystal prompted me to map a few fields, which I did, and could then run the main report again without error.

My concern is this: if I have a job running daily (sometimes multiple times/day) that rebuilds these SQL database tables, will my users have this same problem when attempting to run the report? Pardon our stone-age world here, but I use CR8.5 developer version and deploy reports by compiling and placing on the user's hard drive. They don't have access to the report itself, to be able to do this verify function.