"Andrew D. Stadler" <[EMAIL PROTECTED]> wrote in message
news:53453@palm-dev-forum...
> (2) Put the user data into a .pdb file and associate it with the program.
> Q: OK to have a >64k .pdb file?
Yes.
> Q: How do I assure that the
> .pdb file will travel with the program, if the program is backed up /
> copied / beamed ?
In Palm OS 4.0, you can set the bundle bit on the data database. Your data
database must have the same creator as your application. This causes the
database to be beamed (and copied between main memory and an expansion card)
along with the application on 4.0 devices. It has no effect on older
devices. Backup is independent for each database. Just set the backup bit on
the application and data databases (and don't have a conduit).
If you want a solution that works on older OS'es, you'll need to use your
first idea, or something like it. Let me see if I can explain how I think
segments work. I'm not an expert on this, but I'm sure people will correct
me where I go astray. :)
If you have a lot of code in your application, you split it into multiple
segments. When you build your application, each of these segments get
converted into a code resource. These code resources are put together with
the other resources you've created (after munging them thru the post-linker)
to create a single resource database. So you don't have to worry about
"putting each .r file into its own segment". Each of your data resources
must be under 64K, but they aren't grouped together into segments of
restricted size.
--
Danny
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
