Peter Hamilton-Scott wrote:
Robert, thanks for the snippet. I'll 'tear' it to pieces and see if I
can fathom out the technique involved. 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. In
one book I have they use the appinfo/control record for storing the
sort order required when navigating the records. In this case I
probably don't need an appinfo block, but a control record makes more
sense. I don't know if you can in fact separate the two?
And if you can, what 'value' does the appinfo block add to the
database that a control record on its own could not do?
The appinfo block in the snippit I provided is created by default, and
it is not really any more than a header for the database, and a list of
the records in the db. You CAN add much more complication to the
appinfo block, such as the sort info, but you don't need to. The db
needs to have at least this basic header info, or it it just a bunch of
bits, not a database. Bob.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
