At 08:37 AM 6/8/00 -0400, you wrote:
>
>Well, to my surprise, the pc-side files (I'm particularly interested in
address.dat)
>are certainly _not_ in any sort of easily designed format. So far the
best I've
>gotten is an terse filespec that I'm having a hard time applying from
someone who
>took the time to sweat out the details and this from the palm website
>
>""""The desktop data files (*.dat, *.aba, *.dba, *.tda) are the result of
serialized MFC objects, even the files on the Macintosh.
>The format of the serialized objects produced by MFC is controlled by
Microsoft, and is not currently documented by them.
>
>The way that data is obtained or put into the file is through the use of
the MFC objects using the API in the Conduit SDK. This is
>accomplished by using \condsdk\src\basemon.cpp and basetabl.cpp.""""
>
Don,
This should be a sufficient explanation of the file formats used. To
restore the "objects" from these files, get a hold of the C++ classes used
to implement the objects and simply use the MFC serialization mechanism.
The source for the Palm OS address book application is available, so I
assume the source for a lot of the PC side of things is available too
(sounds like it's in asemon.cpp and basetabl.cpp). If you have Visual
Studio then you have MFC, so the serialization stuff should be easy.
Even if you can't get the source for the C++ classes used, the source for
MFC is available, so you should be able to work out the structure of the
objects given the mechanism, the original data and the save files.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
