B
Bill Gage
I have a need to force the Windows XP date to remain
constant on a database server computer.
The reason is that we use the server for demonstrations
for clients. The database information reflects a current
time period and we would like date on the machine to
remain constant, so when the demo (Client) applicaiton
accesses the data on the Server it will appear to be at a
time in the past that would make the data seem more
current.
That said.
I developed an application that would force the date of
the server machine to reset itself to the date we wanted
(lets say 2/1/2003) every 30 seconds. Also when it sets
the date is also sets the time to whatever the current
time is on the machine. We are taking a different
approach to this in order to hopefully resolve our
problem, by just setting the date once a day when we know
we are doing a demo. So the 30 second thing won't happen
anymore.
Our demo (Client) application started locking up about 1
hour and 20 minutes into the demonstration. We have not
been able to figure out why. However we are starting to
thing it was because our constantly resetting the date on
the machine every 30 seconds.
Does Windows XP do anything regularly in the background
that would conflict with this?
Also does Windows XP do anything that is date dependant
that would cause conflict with resetting the date on the
machine to a date in the past?
Bill
constant on a database server computer.
The reason is that we use the server for demonstrations
for clients. The database information reflects a current
time period and we would like date on the machine to
remain constant, so when the demo (Client) applicaiton
accesses the data on the Server it will appear to be at a
time in the past that would make the data seem more
current.
That said.
I developed an application that would force the date of
the server machine to reset itself to the date we wanted
(lets say 2/1/2003) every 30 seconds. Also when it sets
the date is also sets the time to whatever the current
time is on the machine. We are taking a different
approach to this in order to hopefully resolve our
problem, by just setting the date once a day when we know
we are doing a demo. So the 30 second thing won't happen
anymore.
Our demo (Client) application started locking up about 1
hour and 20 minutes into the demonstration. We have not
been able to figure out why. However we are starting to
thing it was because our constantly resetting the date on
the machine every 30 seconds.
Does Windows XP do anything regularly in the background
that would conflict with this?
Also does Windows XP do anything that is date dependant
that would cause conflict with resetting the date on the
machine to a date in the past?
Bill