Data Driven Query - Milliseconds

DTS
Transferring data from one table to another using 'Data Driven Query' task
and transformations in VB script with
DTSDestination("MyDate) = DTSSource("MyDate")
both fields are with datatype 'DATETIME'
After the transfer, I noticed - Destination table field (MyDate) is WITHOUT
milliseconds , whereas my Source table field(MyDate) is WITH milliseconds.
Any Thoughts '
Thanks
SOn Wed, 7 Apr 2004 15:07:54 -0500, "MS User" wrote:

>DTS
>Transferring data from one table to another using 'Data Driven Query' task
>and transformations in VB script with
>DTSDestination("MyDate) = DTSSource("MyDate")
>both fields are with datatype 'DATETIME'
>After the transfer, I noticed - Destination table field (MyDate) is WITHOUT
>milliseconds , whereas my Source table field(MyDate) is WITH milliseconds.
The problem is caused by the conversion of the datetime to a Variant in
VBScript. The conversion chops off the milliseconds:
http://support.microsoft.com/defaul...;EN-US;Q297463&
Discussed in reference to DTS here:
http://groups.google.com/groups? th...phx.g
bl
( http://tinyurl.com/3f63m )
cheers,
Ross.
--
"There is more to life than simply increasing its speed." - Mahatma Gandhi

Data Driven Query - Milliseconds

DTS
Transferring data from one table to another using 'Data Driven Query' task
and transformations in VB script with
DTSDestination("MyDate) = DTSSource("MyDate")
both fields are with datatype 'DATETIME'
After the transfer, I noticed - Destination table field (MyDate) is WITHOUT
milliseconds , whereas my Source table field(MyDate) is WITH milliseconds.
Any Thoughts ?
Thanks
S
On Wed, 7 Apr 2004 15:07:54 -0500, "MS User" wrote:

>DTS
>Transferring data from one table to another using 'Data Driven Query' task
>and transformations in VB script with
>DTSDestination("MyDate) = DTSSource("MyDate")
>both fields are with datatype 'DATETIME'
>After the transfer, I noticed - Destination table field (MyDate) is WITHOUT
>milliseconds , whereas my Source table field(MyDate) is WITH milliseconds.
The problem is caused by the conversion of the datetime to a Variant in
VBScript. The conversion chops off the milliseconds:
http://support.microsoft.com/default...EN-US;Q297463&
Discussed in reference to DTS here:
http://groups.google.com/groups?thre...0a% 40phx.gbl
( http://tinyurl.com/3f63m )
cheers,
Ross.
"There is more to life than simply increasing its speed." - Mahatma Gandhi

Data Driven Query - Milliseconds

DTS
Transferring data from one table to another using 'Data Driven Query' task
and transformations in VB script with
DTSDestination("MyDate) = DTSSource("MyDate")
both fields are with datatype 'DATETIME'
After the transfer, I noticed - Destination table field (MyDate) is WITHOUT
milliseconds , whereas my Source table field(MyDate) is WITH milliseconds.
Any Thoughts '
Thanks
SOn Wed, 7 Apr 2004 15:07:54 -0500, "MS User" wrote:
>DTS
>Transferring data from one table to another using 'Data Driven Query' task
>and transformations in VB script with
>DTSDestination("MyDate) = DTSSource("MyDate")
>both fields are with datatype 'DATETIME'
>After the transfer, I noticed - Destination table field (MyDate) is WITHOUT
>milliseconds , whereas my Source table field(MyDate) is WITH milliseconds.
The problem is caused by the conversion of the datetime to a Variant in
VBScript. The conversion chops off the milliseconds:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q297463&
Discussed in reference to DTS here:
http://groups.google.com/groups?threadm=036f01c3bdc0%2494bbc510%24a101280a%40phx.gbl
( http://tinyurl.com/3f63m )
cheers,
Ross.
--
"There is more to life than simply increasing its speed." - Mahatma Gandhisql