In addition, since it was mentioned that the database is huge, I would
directly suggest taking the approach of breaking up and then reassembling
the file. As Danny points out 64k is the limit of this technology and it
looks like you're going to need more.
Finally, using ExgDBRead has the additional extra of allowing to to put a
little compression/decompression mechanism that would save lots of time
during hotsync. It's a bit harder to implement, but it pays if you are to
use larger databases.
- bobby
-----Original Message-----
From: Danny Epstein [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 06, 2000 12:19 PM
To: Palm Developer Forum
Subject: Re: Combining a .pdb with a .prc
"Aaron Ardiri" <[EMAIL PROTECTED]> wrote in message news:32330@palm-dev-forum...
> what you will need to do is break up the .prc and rebuild it with
> the new resource.
If you look at the prc/pdb format documentation, you'll see that the last
resource/record extends until the EOF. It's size isn't encoding anywhere
else. So if you could arrange for a placeholder resource to be at the end of
your prc, you could just trim off the placeholder resource's contents, and
append your own resource contents (the pdb file). Then you could use
DmCreateDatabaseFromImage to create a real database from the resource. I
think the resource size would be limited to 64K or so. Also, the resource
would continue to exist along with the real database, doubling your space
requirements. You could delete the resource after you use it, but that would
still require twice the space temporarily. If you want to avoid this, you'll
have to use ExgDBRead to create the database from resources a chunk at a
time, deleting the resources as you go.
--
Danny Epstein
OS Engineer, Palm Inc.
--
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/tech/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
