you can believe me, that I do a) thought about endian problems, b) checked the endian converted version of the number (quite easy if msb and lsb start with 0x3.) and c) checked the contents of my backup directory. The databases in the backup directory are with dates based on time_t, therefore starting from 1.1.1970. You may want to check your backup directory too.
Henk
Dave Lippincott wrote:
It hasn't been my experience that the backup conduit works with PC based dates. I have an application that relies on the backup conduit to transfer the data. I've found all dates in the PDB header are based from 1-1-1904 (with or without the backup conduit transferring the file). The issue I had when I started was problems with the PC forcing time zone correction for UTC on the converted dates and maintaining the proper byte ordering. There are conduit API routines that do the proper date-time conversions. Look up past messages in conduit forum on time conversions or the look over the conduit API docs. Of course, you can always custom encode your date-times using BCD or strings. It takes the guess-work out of converting during a sync but does add some over-head.
-- ------------------------------------------------------------------------- [EMAIL PROTECTED] www.metaviewsoft.de <A HREF="http://www.handango.com/PlatformTopSoftware.jsp?authorId=95946";> <IMG SRC="http://user.cs.tu-berlin.de/~jonash/werbung_palmos.jpg";></A> ------------------------------------------------------------------------- -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
![http://user.cs.tu-berlin.de/~jonash/werbung_palmos.jpg"](http://user.cs.tu-berlin.de/~jonash/werbung_palmos.jpg"){kind=link}