AFAIK
your code CANT slow the system clock...
your code may inadvertently SET it using the DATE or TIME method.


keepITcool

< email : keepitcool chello nl (with @ and .)
< homepage: http://members.chello.nl/keepitcool


"Martin" wrote:

I have a procedure that runs from 07:45 to 17:00. The procedure itself
appears to be slowing the system clock in that this computer now shows
system time as 14:39, whereas the computer next to it (and
unconnected) shows the correct time of 14:44.

I know I can reset the system clock by rebooting, is there any way
that VBA can be used to reset the clock within another procedure? Or
VB or Windows API calls or anything??

Thank you
Martin