2 of 2 people found this helpful
SQL Server 2012 introduced a datetimeoffset data type that gives the type of behavior you are describing. If the field is that datatype, then you may need to create a view for the table in question and for that field cast or convert it to a normal datetime -- e.g. CAST(date_field AS DATETIME)
Hope that helps!
It does, thank you.
The srver is 2008 and the field is a time(7). Changing to datetime or varchar did the trick. Thanks!