Record locked
Richard Kreiss
rkreiss at gccconsulting.net
Fri May 8 11:23:05 PDT 2015
FP on Windows server 20008 and both local employees accessing filePro through a mapped drive and outside employees accessing using RDP to a communication server using a mapped drive.
I received a call from a client about a record which was locked and he could not figure who or what was locking the record.
I manually end RDP sessions that were disconnected and then used RDP to log into the database server. I ran process explorer and found that one report was hung up. One report is run for each record in a particular file. The only time a lookup is done to the file with the locked record is during the select process to get the person's last name for the sort. See below
do_sort◄ If:
Then: lookup mark = l_patient_market k=4 i=K -nx
18 ------- - - - - - - - - - - - - - - - -
◄ If: NOT mark
Then: END
19 ------- - - - - - - - - - - - - - - - -
◄ If: mark(25) ne "6" and mark(40) ne "X"
Then: END
20 ------- - - - - - - - - - - - - - - - -
◄ If:
Then: LastName=mark(1);FirstName=mark(2)
21 ------- - - - - - - - - - - - - - - - -
◄ If:
Then: Select
22 ------- - - - - - - - - - - - - - - - -
◄ If:
Then: sort2=LastName{Firstname
23 ------- - - - - - - - - - - - - - - - -
◄ If:
Then: END
My question is, why would this lookup cause the record to be locked? Or, was the record locked and the select got hung up waiting for the record to become unlocked before proceeding?
Once I killed the processing running this report, the record was unlocked and all of the reports behind ran normally.
Richard Kreiss
GCC Consulting
Office: 410-653-2813
More information about the Filepro-list
mailing list