You're assuming too much. You're reading in a timestamp from a file system,
storing it into a variable, passing it to SQL and storing it in a database.
Have you looked at the value:
a) on the file system
b) once it's in your .Net variable
c) once you've passed it to SQL (is it a stored procedure with a datetime
data type? a string datatype? or a straight SQL statement?
d) stored it in a sql variable (again, a dateTime? a smallDateTime? a
string?)
I've had problems in web pages passing dates back to SQL and losing
precision. It's not just "dotnet", it's the file system, dotnet and SQL all
passing data back and forth. This may not be the source of your problem but
I would certainly look at it more closely.
"Lloyd Sheen" <sq*******************@tostopspamhotmail.com> wrote in message
news:co*******************@twister01.bloor.is.net. cable.rogers.com...
Full path of the date is -
1. Scan all files in several folders
2. Store date of last change in SQL Server
3. Retrieve date from SQL Server and compare to last change date of file
It is so hard to believe that data-in is not equal to data-out.
With dot.net everything that should be simple (at least according to MS)
is not.
Lloyd Sheen
"emg" <emg no sp**@comcast.net> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl... It's possible that the display format lacks the same level of precision
as the actual variables. In other words, var1 may have hours, minutes,
seconds and hundreths of seconds while var2 either doesn't have hundredths of
seconds (:00) or the hundredths value differs.
"Lloyd Sheen" <sq*******************@tostopspamhotmail.com> wrote in
message news:dU******************@news01.bloor.is.net.cabl e.rogers.com... Below is the output from command window. This shows values of
variables and result of comparison.
Make no sense except to dot.net.
Any ideas??
?pofile
#11/11/2003 12:39:22 PM#
?pdtdbdate
#11/11/2003 12:39:22 PM#
?pofile=pdtdbdate
False
Lloyd Sheen