"silverfox" <dcfrench@gmail.com> wrote in message
news:1185648526.721441.325200@i13g2000prf.googlegroups.com...
>I was surprised to find that DateTime.Now.Ticks on my Pocket PC always
> returns a value like 633212192210000000. And about 4 seconds later the
> value returned is 633212192250000000. You always get seven zeros on
> the end, meaning that there are no significant digits past the
> seconds. I need at lease tenth second accuracy for my application.
> Is there a way? I am using VB, for what it is worth.
>

On Jul 28, 1:30 pm, "<ctacke/>" <ctacke[at]opennetcf[dot]com> wrote:
> DataTime.Now on most Windows CE devices is only valid to the second. If you
> need sub-second resolution, use Environment.TickCount, which is milliseconds
> (watch for wrap). If you need even finere, the P/Invoke
> QueryPerformanceCounter.
>
> --
>
> Chris Tacke, Embedded MVP
> OpenNETCF Consulting
> Managed Code in an Embedded Worldwww.OpenNETCF.com
>
> "silverfox" <dcfre...@gmail.com> wrote in message
>
> news:1185648526.721441.325200@i13g2000prf.googlegroups.com...
>
> >I was surprised to find that DateTime.Now.Ticks on my Pocket PC always
> > returns a value like 633212192210000000. And about 4 seconds later the
> > value returned is 633212192250000000. You always get seven zeros on
> > the end, meaning that there are no significant digits past the
> > seconds. I need at lease tenth second accuracy for my application.
> > Is there a way? I am using VB, for what it is worth.