Hello all, I have a report which connects to a Pervasive database via an ODBC connection on the reporting server (RS2005). When I initially bring the report up, a time field (OdbcType.Time) shows the correct format: hh:mm:ss. When I sort any of the sortable columns on the report, the time field (which is not sortable) values all change to 0. Backing out of the report and re-running it restores the correct time values. Any ideas?
Thanks, KenThis issue could be related to the data type of the field. There is a fixed set of data types RS supports: string, boolean, numeric, datetime, timespan. When you sort, we have to use the data we temporarily store (so that we don't have to query the data source) to process the report. If it's not one of the types supported, it might cause the loss of the value. Can you check what CLR type the time field is of?|||Hi Fang, Please forgive my ignorance, but I'm not sure what the 'clr' type is. VS2005 says the table field type is OdbcType.Time. If I try to convert it to something silly, VS2005 complains that type 'TimeSpan' cannot be converted to the silly type. So I guess the CLR type is TimeSpan?|||Can you check your RDL file? Look under the <Field> element of that field, what's the value for <rd:TypeName>?|||Thanks for your time Fang, I've pasted the snippet for the field in question:
<Field Name="TIME_RECEIVED">
<rd:TypeName>System.TimeSpan</rd:TypeName>
<DataField>TIME_RECEIVED</DataField>
</Field>|||Hmm, we have not seen this problem before. Can you submit it along with your .rdl and .rdl.data files at https://connect.microsoft.com/SQLServer? We'll investigate it. Thanks.|||Thank you Fang. I have submitted a bug report and uploaded the files.|||Thanks. We have investigated the issue and the fix will hopefully be included in the next service pack.
No comments:
Post a Comment