Very Computer

by **Ric Griff** » Thu, 11 May 2000 04:00:00

All SQL 7 sp1 on NT 4.0 sp5 tables reflect the true date/time, however, when
DTS moves it to our FoxPro tables, it changes it to an offset 12 hours. Most
of the time this does not occur. It seems to happen every 20 to 50 records.
For example, SQL shows a time of 0100 and the record after DTS will show
1:00pm

Any suggestions would be appreciated.

Thanks,

Ric Griffy, MCP

by **Tibor Karasz** » Fri, 12 May 2000 04:00:00

I'd do a SELECT CONVERT in the SELECT query (source), and convert the
datetime data to string (thus have control over the representation).

--
Tibor Karaszi, Cornerstone Sweden AB
MCDBA, MCSE, MCSD, MCT, SQL Server MVP
Please reply to the newsgroup only, not by email.

Quote:> All SQL 7 sp1 on NT 4.0 sp5 tables reflect the true date/time, however,
when
> DTS moves it to our FoxPro tables, it changes it to an offset 12 hours.
Most
> of the time this does not occur. It seems to happen every 20 to 50
records.
> For example, SQL shows a time of 0100 and the record after DTS will show
> 1:00pm

> Any suggestions would be appreciated.

> Thanks,

> Ric Griffy, MCP

Very Computer

DTS causes 24hour clock time to change to am/pm and loses or gains 12 hours

DTS causes 24hour clock time to change to am/pm and loses or gains 12 hours

DTS causes 24hour clock time to change to am/pm and loses or gains 12 hours