Hi,
we have an custom app used on Tungsten-W and Treos that logs the current
date/time using TimGetSeconds() followed by TimSecondsToDateTime() to
extract the date and time components. Sometimes we get a wrong result
(off by as much as a couple of days, but not totally corrupted).
Of course we have not been able to replicate the behavior, all we have
is the data that is sent by the application through GPRS network connection.
In your opinion where should I look and what would be the best approach
for that kind of bug? Are there any known cases where
TimSecondsToDateTime() would not convert correctly?
Thanks.
Jerome
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
