Sorting Items on a Screen

[Pickering, John (NORBORD)]

Nancy:  By definition, entries in an Image manual master are stored in the
sequence of the hashed values of the key. So for users this is essentially
random -- no amount of deleting, adding or reloading will change this.

Carol:  If you need entries from an Image manual master is some sequence
other than the apparent random sequence of the hash algorithm then you'll
need to build that yourself. I can think of several ways:

- a ghost screen or an initialize procedure which reads the entire master
file, sorts it and creates a temporary file (subfiles in Quick make this
*so* much easier than in the olden days) in the correct sequence which is
then used as the primary file in the display screen (the real master file
can be a secondary)
- some form of external indexing -- parallel ksam file, third party indexing
-- which will require extra code somewhere in your app and probably in more
than one place
- Image's newly added feature to allow sorted and partial key search in
masters -- but this will require PH 8.39
- a database change to turn the manual master into a detail with some key
sorted on the value in your "code" field or a reload of the dataset in code
sequence whenever a new code is added
- big assumption here -- I'm guessing that your manual master is connected
to a detail with the values for each of the codes, right? -- if so then how
about a code and corresponding table for the values of the code? -- you
could then use this detail to drive the display screen

Regards,
John Pickering

> -----Original Message-----
> From:	Nancy Tietz [SMTP:ntietz@mcare3.med.umich.edu]
> Sent:	Thursday, October 12, 2000 11:44 AM
> To:	'Carol Kaffenberger'; powerh-l@lists.swau.edu
> Subject:	RE: Sorting Items on a Screen
> 
> I'm sorry, I didn't read your whole message... the Suprtool solution is
> great for displaying records, but you want to update.  Perhaps you can try
> linking back from the sorted file to the manual master.  
> Another idea is to sort your records at night so that when the user uses
> the
> find procedure, the records come up in sorted order because the dataset is
> sorted in that order.  This is often not feasible and even messy when the
> dataset is a manual, because you can't delete them and add them back in
> with
> details attached.  
> nt
> 
> 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.