index problem

[GCC Consulting]

> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com 
> [mailto:filepro-list-bounces at lists.celestial.com] On Behalf 
> Of Kenneth Brody
> Sent: Tuesday, November 23, 2004 9:33 AM
> To: rkreiss at gccconsulting.net
> Cc: Filepro 2 List
> Subject: Re: index problem
> 
> GCC Consulting wrote:
> > 
> > I have a program which has been running for over 2 years 
> without a problem.
> > Last week the program kicked up an index error.
> > 
> > The program runs from @once in a file called inquire.  The 
> user enters 
> > an order # and the program checks file ls_850 to insure it 
> is a valid 
> > order.  The index is index b and the error says run index 
> maintenance.
> > 
> > I have deleted the lockfile & the index from the command prompt and 
> > then rebuilt the index.
> 
> Any reason you deleted the lockfile?  Did it say someone was 
> in the file?
> Are you certain that nobody was using it?
> 
> > I even changed the method of lookup and used index A - order number 
> > and still received the error.
> > 
> > I commented out lines 14 & 15, the lookup, and the report 
> ran just fine.
> 
> Could the index be getting corrupted from somewhere else?  I 
> notice that this processing doesn't modify that file.
> 
> Does it always fail, or only on occasion?  On every order 
> number, or only some?
> 
> [...]
> > 10do_recIf:
> >   Then:lookup inq = inquire r=r -n
> > 11 If:locked(inq)
> >   Then:r=r+"1";GOTO do_rec
> 
> On a side note, line 11 will never be executed, as the lookup 
> can never fail due to the record being locked.


Last week it failed on a different order.  This procedure is only run once a
week for one customer order for one of their mills.

Ken, I changed the code to use ls_850\index.A which is built on the order #.
This failed also.

I spoke with John and he thought it might be a corrupted record.  But wouldn't
this cause an index error in IUA on ls_850?  If I go in in IUA on either index,
I am taken to the correct order with no index maintenance error message.

If I have time in the next 2 weeks, I am going to archive old orders, move
current orders to a holding file and then delete the key segment.  I'll then
rename the holding key to key and rebuild the indexes and test the program.
Maybe it is a corrupted record.

Richard Kreiss
GCC Consulting