creating usable records - warning: long question

[GCC Consulting]

To add to John's post, To make this transition easier you could add a control #
field and then set it equal to the record number,  Then simply create an auto
index on this field, modify your lookups to use an indexed lookup.  
 
The last think you will need to do is create a method for getting the next
control #.
 
I did this many years ago for a friend who had build an item master based of
record number lookups as he thought this was faster then an indexed lookup.
Also, the computers were much slower and rebuilding an index of 10,000 items
took quite a while.
 
This is not a painless solution, but it is a good one.
 
By the way, I still use record number lookups when updating or deleting records
from a browse lookup.  It insures that I get the proper record when the primary
key is the same i.e an order or invoice # even when there is a secondary key
(product # or line #).
 
Richard Kreiss
GCC Consulting 


  _____  

From: filepro-list-bounces at lists.celestial.com
[mailto:filepro-list-bounces at lists.celestial.com] On Behalf Of Leefp1 at aol.com
Sent: Sunday, May 30, 2004 3:55 PM
To: filepro-list at seaslug.org
Subject: Re: creating usable records - warning: long question


In a message dated 5/30/2004 3:41:56 PM Eastern Daylight Time,
lgf at lgfcomputers.net writes:

With all the uses of indexes, why would you have to use record numbers ?
 
Ed Hilovsky
LGF Computers

Your question, of course, points out what I talked about at the end of my
original post.  I know that using recond numbers is not the best, but I have
been so doing for many years.  To undo the basic structure of my application
would not be worth the gains resulting from now doing it right.
 
-Lee
----------------------------------------------
Lee B. Walker
Walker & Company
5307 Front Royal Drive
Cross Lanes, WV 25313
304.419.0013
lee at walkeronline.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.celestial.com/pipermail/filepro-list/attachments/20040601/0910e47e/attachment.html