Thanks, fluteplr and tlbroadbent, for your responses to my earlier post. I have a bit more information and am hoping you can keep me going.
The field looks like this:
}sÓ
when it is imported from the H-P. From the vendor technical info, I see it is a 6-byte field mapped to different portions of the date & time in different positions. For example
(0:12) Year (0 . . 4095)
(12:4) First 4 bits of Julian date
I didn't have any luck with CDate or FormatDateTime (tried CStr too, while I was at it). The table imports OK, without an error, but the timestamp field still looks like the example above. I'm not finding anything in SQL Server help on these functions. Any further ideas? Thanks a lot.
The field looks like this:
}sÓ
when it is imported from the H-P. From the vendor technical info, I see it is a 6-byte field mapped to different portions of the date & time in different positions. For example
(0:12) Year (0 . . 4095)
(12:4) First 4 bits of Julian date
I didn't have any luck with CDate or FormatDateTime (tried CStr too, while I was at it). The table imports OK, without an error, but the timestamp field still looks like the example above. I'm not finding anything in SQL Server help on these functions. Any further ideas? Thanks a lot.
