Hi All,I have a completely unresolved problem here (three people in our team have looked without solution). In our test server, I made a SSMS stored procedure that returns (among others) a datetime field, which is used in the dataset of a report. I ran the report and saw that the field (CreateDate) displayed correctly as a datetime with the field format of "dd/MM/yyyy HH:mm" as requested in the spec. The report was signed off and added to our live report solution in SSRS, but we soon received a complaint that all the times were showing as 1 o'clock in the morning.We have a function to convert the database GMT to display BST, which adds one hour to the displayed time at this time of year, so I would expect this result if the SSMS query was finding a date, not a datetime, then adding one hour for BST and giving that to SSRS. This implies that the report is receiving a datetime, as the function is run as part of the SQL query in the stored procedure.I checked everything I could think of and can see no reason why the test version would return a correct datetime field, while the live version would return this datetime field that looks as though it came from a date field.In the end, I added a new datasource to the live report, referring back to the test server - the times display correctly, which seems to imply that the problem is somewhere on the server, However, when I run the procedure itself as a query in SSMS, the results include the correct times. I am at a loss to see what is going on here - any suggestions most welcome!Cheers,Mark
↧