Record lock issue when performing lookup within current file

[Richard Kreiss]

Josh,

I had a problem at one client where non-shipped order detail lines were deleted.  The remaining lines were used for invoicing.  No back orders.  This seems simple enough.  However, it presented a problem in that the detail records were be deleted through a browse lookup.  The deletion was done through a GOTO using the a record number lookup to delete the specific record.  By the time the program returned to the browse lookup and re-executed it, a detail record from a newly entered order appeared.  To solve this problem, I had to add a drop routine to insure that only order details from the order being viewed appeared in the browse.  The browse caches the record numbers of the items being displayed.  This allows for faster re-display.  This was not a problem when computers and networks were slower.  However, in my client's environment, the faster speed of the computers and the speed the order clerks were entering order details, allowed a record to be deleted and that same record used again for a new order and displayed when the browse re-executed.

Is this problem similar to the one you are experiencing.  Maybe.

I strongly recommend that you move this application to a header/detail programming as quickly as possible.  The time you spend tracking down this record locking problem should be eliminated by doing the lookups from another file.  Also, you may be able to add some additional fields to the header what will make creating reports much faster in that only one record would need to be selected and not all of the details.  

Richard Kreiss

> -----Original Message-----
> From: Filepro-list [mailto:filepro-list-
> bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Josh Reader via
> Filepro-list
> Sent: Friday, June 17, 2016 11:36 AM
> To: filePro Mail Group <filepro-list at lists.celestial.com>
> Subject: RE: Record lock issue when performing lookup within current file
> 
> It is v5.8 on CentOS 7.  I just made a few adjustments to the code (removed the
> close commands and added a write command after updating the record in the
> lookup) and activated the line syncing again.  I had the 3 buyers here today go
> back to the main menu and in again.  If I have the issue still I'll find out what
> record # it says is waiting to be unlocked.  I believe it was a new record that
> someone was entering in a new PO on but I'll verify.
> 
> Thanks,
> Josh
> 
> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
> Sent: Friday, June 17, 2016 11:23 AM
> To: Josh Reader; filePro Mail Group
> Subject: Re: Record lock issue when performing lookup within current file
> 
> On 6/15/2016 3:26 PM, Josh Reader via Filepro-list wrote:
> > Hi All,
> >
> > I am trying to program a feature for our purchasing dept and running
> > into some lock issues.  Currently when our buyers have a PO line with
> > multiple
> [...]
> 
> What version of filePro is this?  I seem to recall an issue with a protected lookup
> to the current file and a getnext loop could leave records locked, but that was
> fixed quite some time ago.
> 
> Also, do you know what record is giving the "waiting for record to be unlocked"
> message on the other workstations?
> 
> --
> Kenneth Brody
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 12809 bytes
Desc: not available
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20160617/289e9789/attachment.bin>