I could use preferences to do that as I use them anyway for other
purposes. I thought though that it might be more contextual if I keep
database settings etc in the database. No reason why I should but it
somehow seems more appropriate.
SLO Revo News wrote:
As I have your attention is is necessary to have an 'appinfo' block if
all I want is to have a record that is used to keep track of various
features of other records.
Database state doesn't _have_ to be stored in an AppInfo block. You can
also store that type of information in preferences or feature memory if
you find those APIs more manageable. Or even in a separate state
information-only database.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
