Thanks. I know the StrAToI returns an Int32, but it seems to always work casting it to a UInt32. And its off by on day exactly or 86400 seconds so I don't think its a cast/conversion problem.
I'm using the .NET DateDiff function on the server side so I don't think its a problem calculating the seconds. I've checked the values it sends and they are correct. -Dave "Vu Pham" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > ----- Original Message ----- > From: "David Webb" <[EMAIL PROTECTED]> > Newsgroups: palm-dev-forum > To: "Palm Developer Forum" <[EMAIL PROTECTED]> > Sent: Friday, April 16, 2004 9:58 AM > Subject: Any known bugs in TimSetSeconds() ? > > David, > > I have some similar work like yours but on the reversed direction : the Palm > app sends its time back to a Unix server. Although my problem is not the > same like yours, but I would like to list what I met and fixed, just in > case: > > 1. I prevent using StrAToI because it convers to a signed interger. I don't > know if it converts correctly for time on PalmOS that is an unsigned int32 > number. > > Instead of using a string, I sent the time in seconds as an int ( 4 bytes ) > from the Unix host to the PalmOS dev. On PalmOS I cast it to an unsinged > int. By this way, I don't need to use the StrAToI. > > 2. I got an time shift of one day : it is because I calculated the wrong > leap days since 1904 until now. > > Vu > > > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
