Not sure why the time matters application would store dates as integers but that is exactly what it is doing. I was able to contact someone at the remote site and using a few examples to verify things determined that the begin date needed to make this work is {^1800-12-28}.

>>I am remotely connecting to a SQL Server database that is using the program TimeMatters to record phone messages. When I uses ODBC to extract ALL the columns from the phone table, I have a column named date returned as an Integer. The maximum value for the "date" column is 73470.
>>
>>The time value is also odd in that it too is returned as an integer. The maximum value in that column is 83501.
>>
>>All I really want returned is a true datetime column but it is not looking easy. The end users (200 miles away) tell me that the dates show up as normal dates.
>>
>>Anyone else ever experienced something like this and possibly have a solution?
>
>Looks like offset values. If this happens to be true, 83501 is equivalent to 23:11:41 (see SECONDS() function); I would bet something close to {^1801-01-01} as the start date period. So, the datetime value should be recomposable as
>

DTOT({^1801-01-01}+nDate)+nTime