In my TW application I use several Crystal Reports reports. The customer sent me a new version of the report, other than the rpt file and 2 additional parameters for the stored procedure used by the report no big changes.
I've replaced the original report with the new report and added the 2 new parameters. When I try to open the report from the application I keep getting:
Other reports work correctly, just this one report is being naughty :(
Page 1 / 1
Does the report work when you try to run it directly (without the software factory)?
Does the report work when you try to run it directly (without the software factory)?
yes it does….
Doing a quick google I came onto this topic. Could this be the problem you are experiencing? The topic suggest manually linking tables instead of using a view causes issues.
But how can I force the date picker in my Thinkwise application to output the selected date as yyyy-mm-dd rather than the more human readable (on this side of the big Atlantic puddle) dd-mm-yyyy?
@Erwin Ekkel did you see my last response? It seems to be a data formatting issue but I can't figure out how to control it...
@Alban_T :
I'm a bit confused as to why the date is formatted as an nvarchar in the call to reporting_price_and_purchasing_headerinfo_v2. Assuming that all those values are the report parameters that you are passing along: What kind of domain did you give to the report parameter for the dates?
Just trying to rule things out here :)
@Alban_T :
I'm a bit confused as to why the date is formatted as an nvarchar in the call to reporting_price_and_purchasing_headerinfo_v2. Assuming that all those values are the report parameters that you are passing along: What kind of domain did you give to the report parameter for the dates?
Just trying to rule things out here :)
Maybe that is a Crystal Reports thing? The report parameters in Thinkwise are setup with the “date” domain which is effectively a normal SQL DATE datatype:
Hi @Alban_T,
I'm not exactly sure where this issue lies, it could very well be related to Crystal Reports. I understood that there were previously some issues with certain date/datetime/datetime2 data types in combination with Crystal Reports parameters. Perhaps that it works when a ‘date_time’ data type is used?
In any case, it's been a month now, so it might also be a good idea to ask if you still need support with this. In that case, a TCP issue might be more appropriate.