Hi Warren, > >you should use 'the milliseconds', that will return you an integer (which > >value is the number of milliseconds since the computer - or the OS - has > >started ... IIRC) > > I thought of that one too -- but if the machine's been on (booted) > for more than twenty-odd days, the milliseconds exceeds the > maxinteger and wraps into a negative value. :\
This reminds me a question I've asked on our french MMUG some weeks ago, without having a solid-as-rock answer. Does the #timeStamp property of the messages sent by the shockwave multiuser server also warp down to negative values? (because as the smus is on a dedicated server, this machine run for a long time, but it seems I havn't yet seen negative values... although it's been running for 7 months now (ok I'm not monitoring timestamt values everydays!, but as I had that in mind for a while I 've checked from time to time without noticing a wrap!) (I think I never notice the wrap because the timestamp is set back to 0 each time the movie is created on the server... ) Does anyone know something more about this? any comments/feedback/experiences welcome! .s�b [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
