From: maint72@saad-emh1.ARMY.MIL (Michael Gordon)
Newsgroups: comp.databases.informix
Subject: Perform Ordering.
Date: 9 Oct 92 18:18:05 GMT
Reply-To: maint72@saad-emh1.ARMY.MIL (Michael Gordon)
X-Informix-List-ID: <list.1512>


>> Received: from rmy.emory.edu by saad-emh1.ARMY.MIL id aa10583;
>>          8 Oct 92 22:41 EDT
>>Received: by
>>        rmy.rmy.emory.edu (5.65/Emory_rmy.3.3.20) via MAILPROG
>>        id AA06647 ; Thu, 8 Oct 92 22:39:36 -0400
>>Return-Path: ilist@rmy.emory.edu
>>From: kevinc@sequent.com (Kevin Closson)
>>Message-Id: <1992Oct8.224918.20188@sequent.com>
>>Subject: Re: Perform Data Ordering.
>>Date: 8 Oct 92 22:49:18 GMT
>>Reply-To: kevinc@sequent.com (Kevin Closson)
>>Organization: Sequent Computer Systems, Inc.
>>Sender: informix-list-owner@rmy.emory.edu
>>To: informix-list@rmy.emory.edu
>>X-Informix-List-Id: <news.1943>
 

>>In article <9638@emory.mathcs.emory.edu> maint72@saad-emh1.ARMY.MIL 
>>(Michael Gordon) writes:

>>>     The answer to your question is, YES.
> 
> 
>>>          1.   Open the TABLE and check for INDEXED fieldnames, the
>>>               fieldnames for last_name and first_name must be indexed.
>          
>>>          2.   If they are not indexed then modify them to be indexed.
>>>               You can use either DUPS or UNIQUE index, UNIQUE will 
>>>               permit only one like name to be added into the database.
 
 
>>   This technique should only work on static tables.  Should a row of
>> "Johnson" be deleted and then a row of "Smith" be inserted, the ordering
>> will be broken.
 
Kevin,
 
What happened to the rest of my message text, the query statement which
reorders the names fields in a temp file and displays the names in correct
order?
 
Query lastname using '>= A*' <return> and query firstname using '>= A*' 
<return>.
 
Your statement about "... the ordering will be broken." is true whenever
a row is deleted and a new row is added, however, without creating a massive
set of code to perform this automatically this seems the simplest means
to achieve the end product.  Of course we could create a custom menu
program for the user for table queries only and imbed the query commands 
within the menu statements.  I believe that by instructing the users of the
database in the advantages of SQL they become more versatile and self 
sufficient, thereby requiring less "babysitting".
 
Have you discovered a better method to resort fields for the user?
 
Is so, could you pass it along?
 
Have a good day and a nice holiday.
 
 



					Michael S. Gordon
					Foreman, Gyroscope Section
					Avionics Division 

 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 *                                                                           *
 *  Michael Gordon                           Sacramento Army Depot           *
 *  Foreman, Gyroscope Section               Directorate For Maintenance     *
 *  E-Mail: maint72@saad-emh1.army.mil       Attn: SDSSA-MAV-320             *
 *  DSN:    839-2367                         Michael S. Gordon               *
 *  Comm.:  (916) 388-2367                   Sacramento, CA 96813-5036       *
 *                                                                           *
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *