>I am puzzled. I have a server that is running NT 4.0, and all the clients are Windows 95. I have an application running across the network. Part of this application is to store date and time attributes of files for comparisons later. When daylight savings occurs the actual dates of the files being reported to the client is exactly 1 hour ahead or behind depending on which daylight savings period we are in. An example is say friday a time on a file would be 13:00:00 on friday. Over the weekend daylight savings occurs, and on monday the time on the file now will show 14:00:00. This then stops the application from running. I know there has to be some windows call to obtain UTC time and offset. Is this correct? Is this proper behavior under NT 4.0 ? , any help ???

Mark,

There is a function (GetTimeZoneInformation) in the API which indcludes the date and the offset from UTC time. Unfortunately, it requires a structure and, for some reason, VFP keeps crashing whenever I try to access it, and I've tried several methods, all with the same result.

There is another function, however, to convert a time to UTC. If you're interested, please post.