On Wed, 7 Apr 1999 [EMAIL PROTECTED] wrote:
> I like to keep more than one sorted record list for my application
> database, each ordered on a certain field of the records, so that the
> application doesn't have to sort the records on the fly (it's mainly a
> read-only database, so maintaining the lists is less concerned).
> Currently, the PDB itself keeps one record list. To maintain the extra
> sorted record lists, I can think of two ways. I can put each of them in
> a separate PDB file, which would just contain the record ids in the
> desired order. Another approach is to dedicate a special record in the
> PDB for storing the list. Are there other approaches that people
> recommend? Thanks.
There is a block reserved for sorting data, called the "Sortinfo Block",
analagous to the "Appinfo block". Do _NOT_ use the sortinfo block, as
there are a number of bugs relating to it and HotSync. Do not use the
Appinfo block, either, as some bugs limit it to 512 bytes.
One benefit of using separate databases is that it is easy to discard the
indexes, which can be useful if they can be regenerated at the cost of
some computation. If I remember correctly, the Expense tracker uses just
this technique.
--
Kenneth Albanowski ([EMAIL PROTECTED], CIS: 70705,126)
