<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META charset=US-ASCII http-equiv=Content-Type
content="text/html; charset=US-ASCII">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; BACKGROUND-COLOR: #ffffff">
<DIV dir=ltr align=left><SPAN class=599441416-01062004>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. </SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=599441416-01062004></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=599441416-01062004>The last think you will
need to do is create a method for getting the next control #.</SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=599441416-01062004></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=599441416-01062004>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.</SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=599441416-01062004></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=599441416-01062004>This is not a painless
solution, but it is a good one.</SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=599441416-01062004></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=599441416-01062004>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 #).</SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=599441416-01062004></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=599441416-01062004><!-- Converted from text/plain format -->
<P><FONT size=2>Richard Kreiss<BR>GCC Consulting </FONT></P></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma><B>From:</B> filepro-list-bounces@lists.celestial.com
[mailto:filepro-list-bounces@lists.celestial.com] <B>On Behalf Of
</B>Leefp1@aol.com<BR><B>Sent:</B> Sunday, May 30, 2004 3:55 PM<BR><B>To:</B>
filepro-list@seaslug.org<BR><B>Subject:</B> Re: creating usable records -
warning: long question<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>
<DIV>In a message dated 5/30/2004 3:41:56 PM Eastern Daylight Time,
lgf@lgfcomputers.net writes:</DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid">
<DIV><FONT face=Arial>With all the uses of indexes, why would you have to
use record numbers ?</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>Ed Hilovsky<BR>LGF
Computers</FONT></DIV></BLOCKQUOTE></DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>-Lee</DIV>
<DIV><FONT lang=0 face=Arial PTSIZE="10"
FAMILY="SANSSERIF">----------------------------------------------<BR>Lee B.
Walker<BR>Walker & Company<BR>5307 Front Royal Drive<BR>Cross Lanes, WV
25313<BR>304.419.0013<BR>lee@walkeronline.com</FONT></DIV></BLOCKQUOTE></BODY></HTML>