index problem

Jeff Harrison jeffaharrison at yahoo.com
Mon Feb 21 13:45:48 PST 2011


----- Original Message ----

> From: Richard Kreiss <rkreiss at gccconsulting.net>
> To: Jeff Harrison <jeffaharrison at yahoo.com>
> Cc: filepro-list at lists.celestial.comf
> Sent: Mon, February 21, 2011 10:40:29 AM
> Subject: Re: index problem
> 
> Quoting Jeff Harrison <jeffaharrison at yahoo.com>:
> 
> >  ----- Original Message ----
> > 
> >> From: Richard Kreiss <rkreiss at gccconsulting.net>
> >>  To: filepro-list at lists.celestial.comf
> >>  Sent: Sun, February 20, 2011 12:15:09 PM
> >> Subject: index  problem
> >> 
> >> A client has been having an index problem after  a status field value
> >> is changed.
> >> 
> >> The record  is accessed from a browse lookup by getting  the record
> >> number  and then doing a
> >> 
[snip]

> > 
> > It is  difficult/impossible to tell why your index is getting corrupted 
>without
> >  seeing all of the pertinent code.  Are you locking the record before the  
>status
> > is updated?  Are your doing a write or close to that  protected lookup when 
>you
> > are done?   When doing something like you  describe, I would do the 
protected
> > lookup, change the data, then close  the file.  After returning from the 
>called
> > process I would have it  re-execute the original browse based on the new 
>data.
> > 

> Jeff,
> 
> The program is updating the current  record and was accessed using @keyS.
> 
> @keyS initiates the sales  routines.It is the index in this "local" file which 
>is having the problem.   The @key locks the record.
> 
> I noticed that I had put a write in in the  called routine just before it 
>returns to the calling input  program.
> 
> Richard
> 

Again, it is difficult/impossible to say without seeing all of the applicable 
code.  Can you isolate this so that it is duplicatable with minimal code?  Then 
perhaps you can post all of that code and we can take a look.

Jeff Harrison
jeffaharrison at yahoo.com
Author of JHExport and JHImport


      


More information about the Filepro-list mailing list