Your answer is a definite maybe.  As long as you a) do not have a sort path
on that chain (other than date and time) and b) you have used DBUPDATE to
update the entries in the chain and do not DBDELETE and DBPUT  to update an
entry, then they should always return to you in chronological order.  By
chronological, I mean the order they were entered into the system, not by
some transaction date order (order date, date received, etc...).  If you
have more than one key in the set and the value of that key has been
changed, or the value of a sort item has been changed, then the record would
have been deleted and put back onto the end of the chain.  This would kill
the chronological sequence of the chain.


--
Stephen R. Daniels
MIS Manager
Park Farms
Canton, OH
330-455-0241   330-455-5820 (fax)
[log in to unmask]


Jim Phillips <[log in to unmask]> wrote in message
news:F4B1826B1A21D211AEC5006008207AF401E247F6@dogbert.csillc.com...
Given an Image detail data set in "natural" condition (that is, no
reorg, no DBUNLOAD/DBLOAD, etc. has been performed on the set),
are the records returned in chronological order when DBFINDing by
the primary path and DBGETting them (mode 5)?

My empirical testing appears to answer this question in the
affirmative, but I wanted to see what you-all had to say.

Jim Phillips                            Manager of Information Systems
Voice: (330) 527-2124                   Therm-O-Link, Inc.
  Fax: (330) 527-2123                   PO Box 285; 10513 Freedom St.
Email: [log in to unmask]       Garrettsville, Ohio  44231