>>I think I've finally got it - by commenting the .SystemToDateTime call in ConvertFileTime AND commenting .LocalToDateTime in ConvertDateTime. Somehow these two cancel each other out and I'm getting the files with correct times and dates. Gee, even centuries are correct :).
>>
>>In the end, I'll have a stick-and-rope (I think it would be called "tin foil and chewing gum" in American terms) version control. It should be able to keep stuff in sync no matter which continent the programmer calls from, by keeping every timestamp tied to server's timezone.
>>
>>If ever we move the server, there'll be just one setting to change in the ini file :).
>
>Glad you got it all straightened out. Shows how much I know my own stuff.< vbg > Hope you didn't have too much trouble getting it to work and that it's been worth the trouble.

Thanks for providing the code in the first place. And tell me about knowing my own code... whenever I look at something I wrote more than a year ago, I either think I was a genius back then and am an idiot now, or vice versa - because it either takes me too long to understand what I was doing, or takes too little to ask myself what was I doing back then :).

And actually this little trip into timezones was fun - best thing to do on a Friday afternoon. Have a good (dark) one (or two...).