After serious thinking Jim Cone wrote :
The VBA Developers Handbook by Ken Getz states that the Timer function
"...can measure time only to 1/18 second accuracy because of the particular
internal timer it's using."
Also, "It turns over as midnight, so if you happen to be running a test over
the bewitching hour, your test results will be meaningless."

Strangely, KB172338 states that the Timer resolution is 1 second vs. 10ms for
TimeGetTime and GetTickCount.
(the summer intern strikes again).<g

Thanks, Jim!
I've been using 4 decimal places which means it's been returning
results to the ten-thousandth of a second. It actually does return any
number of decimals regardless of the accuracy. While accuracy may have
significance in some areas of eval, it's not really an issue for me
when timing running code. As I said, I just use it because it's 'quick
& easy'. If I need greater accuracy I use GetTickCount, though I'm
studying the benefit of using Ron's suggestion in it's place.

Your input is greatly appreciated...

--
Garry

Free usenet access at http://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc