|
Subject:
|
Problem when changing the Location property
|
|
Posted By:
|
armandoa
|
Post Date:
|
10/8/2004 6:21:33 PM
|
We are using Crystal 9.0 Professional for developing our reports and the CR.NET for publishing them on the web. The issue is the following. I programmatically access and change the Location property of the ReportDocument object, to a different database, but using the same stored procedure. When i do this, a formula in the report throws an exception, and tells me that the {?@Epoca} does not exist when it actually does. The strangest part of this is, that if i don't explicity change the location property the report works flawless, but if i change the location, even to the same string that the report current have, then the report throws the exception. We actually don't know why but as soon as we modify this property, even with the same value... it throws the exception.
If i even write this:
foreach(CrystalDecisions.CrystalReports.Engine.Table crTable in oRpt.Database.Tables)
{
crTables.Location = oRpt.Database.Tables[0].Location
}
Thank you.
|
|
