>
> If you need to support Palm OS 3.5 and older, your best bet is to beam a
> single archive containing all the databases, compressed or not. If you know
> that your app exists on the receiving device, you can have it break apart
> the archive into its constituent databases. Otherwise, you'll need to make
> the archive "self-extracting". This is trickier.
any pointers on creating this "self-extracting" archive? I still need to
support < 3.5.
> Note that in some cases you can get away without multiple databases by
> storing default data in resources which are instantiated using
> DmCreateDatabaseFromImage.
in what cases will this work. I have one dabase in particular that could
get somewhat large (20-100k)
thanks!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
