Per,

A chained DBGET will return detail records in chronological order (i.e.,
the order in which they were written), unless you have a sort item in the
chain, or you do something to rewrite records in the dataset, such as
repack the dataset.

At 08:23 AM 11/10/2003, [log in to unmask] wrote:
>I'm wondering how predictable chained (DBFIND and then) DBGETs is. I.e.
>will the (unsorted) chain (always) be in the same order as they were
>written? Initial testing shows that if I write (DBPUT) a few records to the
>(unsorted) detail A, later reading (with DBFIND(master-key) and [loop]
>DBGET,5) will give me the records in the same order they were written. Will
>that always be true? If not, are there special circumstances for when it's
>not true or is it just coincidence that they come back in the order they
>were written? Will reload/structural changes to the database change this?
>Am I missing something fundamental just by asking this?
>
>The normal order of events in this process is that the master-record and
>the detail-records is written *once* without changes/updates, and at some
>later time they are read (and the master updated to "been read"-status)
>*once*. So my first objective is to find out how predictable the reads are
>(changes to DB or programs will probably be painful ;-).

--
Tom Brandt
Northtech Systems, Inc.
130 S. 1st Street, Suite 220
Ann Arbor, MI 48104-1343
http://www.northtech.com/

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *