>Hi!
>
>I am having a strange problem with the lastmodified datetime due to Daylight Savings.
>
>I have an application that takes a snapshot of a network folder tree and saves the path, filename, size, last modified datetime of all files under it into a table, then users keep adding files under that folder tree and then the app compares the tree with the snapshot (stored in a table) and finds out all modified files or new files and then zips them up and uploads them to an FTP server.
>
>All this worked fine till the daylight savings kicked in.
>
>e.g. a file in the snapshot has a datetime of 2003/01/01 9:30 am and that same file on the network now shows its datetime as 2003/01/01 8:30 am. This has happend to every file on the network so now the application thinks that every file has been modified (even though really none of them were modified) and creates this huge zip file. Every file has a 3600 second difference which is one hour.
>
>Has any one encountered this problem?
>
Sarosh,

This problem occurs because Windows stores all the date/time stamps in UTC time and uses the current bias to determine the local time for them. My Windows Time (FILE#9738) can be used to retrieve the UTC file times so that accurate comparisons can be made.