Print Page | Close Window

problem report

Printed From: Crystal Reports Book
Category: Crystal Reports .NET 2003
Forum Name: Writing Code
Forum Discription: .NET 2003 programming API, report integration
URL: http://www.crystalreportsbook.com/forum/forum_posts.asp?TID=699
Printed Date: 28 Apr 2024 at 9:53pm


Topic: problem report
Posted By: andyoneill
Subject: problem report
Date Posted: 19 May 2007 at 6:52am
I have a net 2005 crystal report which I'm loading from a web page.
Reports is based on a stored procedure.
It gives an error saying the parameter is  not set.
The code is very similar to code I have used before.
The report runs fine in the IDE when I manually provide the parameter value.
I put together another (very simple)  report which uses the same stored procedure and hence parameter.
Modified the code slightly to load that report instead.
Works fine.
 
The only slightly odd thing about my report is it originally had a sub report in it which was using this parameter to link.
I removed the sub report to try and reduce the possible causes of problem(s).
The parameter and stored procedure referred to in the error are those of the main report rather than the sub report.
 
So I'm thinking the problem is probably in my report (somehow) rather than the c# loading the thing.
 
OK, maybe a corruption of some sort I thought.
Copy and paste the objects out the original one into my new test report.
But I only get to paste one at a time when I select a bunch to copy.
Which'd mean little time saved over re-writing.
There's pretty complex formatting of lines boxes and whatnot in my report so that'd be a lot of work.
 
I also tried creating a new report based on the original.
No joy there either.
 
Anyone else seen something similar?
Anyone got a way to copy and paste groups of objects from one report to another?
Could I programmatically?
Anyone perhaps got a straw I can clutch at?
 
Thanks in anticipation.



Replies:
Posted By: andyoneill
Date Posted: 22 May 2007 at 1:55am
Well this was a really weird one.
I worked on this project from home over the week-end and resolved the problem.
My home office computer has a different name than that at work and only vs 2005.net.
The report originally had a fully qualified machine name for the server - mailto:P3978@blaa.com - P3978@blaa.com
 
When I "upgraded" the report version and changed the server name it worked.
Bring it bnack to work, change the server name back to an unqualified machine name and it works here.
 
I dunno.
Maybe there was some subtle corruption which changing versions filtered out in the conversion.



Print Page | Close Window