Lockfile question

Fri Sep 15 12:12:44 PDT 2006

> -----Original Message-----
> From: GCC Consulting [mailto:gccconsulting at comcast.net]
> Sent: Friday, September 15, 2006 2:21 PM
> To: 'Don Coleman'; 'filePro'
> Subject: RE: Lockfile question
> 
> 
> 
> > -----Original Message-----
> > From:
> > filepro-list-bounces+gccconsulting=comcast.net at lists.celestial
> > .com
> > [mailto:filepro-list-bounces+gccconsulting=comcast.net at lists.c
> elestial.com] On Behalf Of Don Coleman
> > Sent: Friday, September 15, 2006 1:55 PM
> > To: 'filePro'
> > Subject: Lockfile question
> >
> > Windows 2000 Advanced Server, Win2000 clients, fP5.0.13
> >
> > I have a rclerk process which the user scans a prescription
> > number.  Clerk calls a form and the prescription label
> > prints.  Periodically, at least several times/day the user
> > will receive a filePro error stating:
> >
> > A filepro error has occurred on file:
> > E:\QS1\TODO\FILEPRO\ALLERGY\LOCKFILE
> >
> > Line 156
> >
> > If the user immediately re-enters the app. and scans this
> > number again it will usually process it w/o error and print
> > the label.  This error happens on three different reference
> > files (the file named ALLERGY is one of them).
> > Note that the lookups are not protected and are not posting
> > or writing any data to the lookup file.  They are only
> > filling in lookup data fields into dummy variables on the
> > prescription label (form).  I'm at a loss as how to resolve.
> > The code snippet below is from the form table.  Any
> > suggestions appreciated.  TY.
> >
> >
> >
> > Sep 15, 2006  13:41           File Name: QS1
> >      Page   1
> >                              Processing: 12
> >
> >  155 -------   -   -   -   -   -   -   -   -   -   -   -   -
> >  -   -   -   -
> >          If: 77 eq ""
> >        Then: goto ck2all
> >  156 -------   -   -   -   -   -   -   -   -   -   -   -   -
> >  -   -   -   -
> >          If:
> >        Then: lookup all = allergy  k=77   i=A -nx
> >  157 -------   -   -   -   -   -   -   -   -   -   -   -   -
> >  -   -   -   -
> >          If: not all
> >        Then: LB(34,ALLUP)="";goto ck2all
> >  158 -------   -   -   -   -   -   -   -   -   -   -   -   -
> >  -   -   -   -
> >          If:
> >        Then: LB=all(2)
> >  159 -------   -   -   -   -   -   -   -   -   -   -   -   -
> >  -   -   -   -
> > ck2all   If: 78 eq ""
> >        Then: goto ck3all
> >  160 -------   -   -   -   -   -   -   -   -   -   -   -   -
> >  -   -   -   -
> >          If:
> >        Then: lookup all = allergy  k=78   i=A -nx
> >  161 -------   -   -   -   -   -   -   -   -   -   -   -   -
> >  -   -   -   -
> >          If: not all
> >        Then: LC(34,ALLUP)="";goto ck3all
> >  162 -------   -   -   -   -   -   -   -   -   -   -   -   -
> >  -   -   -   -
> >          If:
> >        Then: LC=all(2)
> >  163 -------   -   -   -   -   -   -   -   -   -   -   -   -
> >  -   -   -   -
> > ck3all   If: 79 eq ""
> >        Then: goto noall
> >  164 -------   -   -   -   -   -   -   -   -   -   -   -   -
> >  -   -   -   -
> >          If:
> >        Then: lookup all = allergy  k=79   i=A -nx
> >  165 -------   -   -   -   -   -   -   -   -   -   -   -   -
> >  -   -   -   -
> >          If: not all
> >        Then: LD(34,ALLUP)="";goto noall
> >  166 -------   -   -   -   -   -   -   -   -   -   -   -   -
> >  -   -   -   -
> >          If:
> >        Then: LD=all(2)
> >  167 -------   -   -   -   -   -   -   -   -   -   -   -   -
> >  -   -   -   -
> > noall    If:
> >        Then:
> > IA(2,*)=mid(36,"1","2");IB(2,*)=mid(36,"3","2");IJ(2,*)=mid(36,"5",
> >              "2")
> >
> > Don Coleman
> > Donald G. Coleman, Consultant
> > 402 Andrew Circle
> > Indiana, PA 15701
> > dcoleman at dgcreact.com
> > (724) 349-6302
> 
> Don,
> 
> Is it possible that someone is accessing these records through IUA?
> 
> This may not be an answer, but have you tried adding something like this
> to
> you lookup
> 
> >  156 -------   -   -   -   -   -   -   -   -   -   -   -   -
> >  look_1      If:
> >        Then: lookup all = allergy  k=77   i=A -nx
> >  157 -------   -   -
> 			LOCKED(ALL) AND CT LT "3"
> 			ct=ct+"1";GOTO look_1
> 
> You could set the counter higher and see if this works.  The lock may be
> tempory and this may help in keeping the clerk from exiting the app and
> coming back in.
> 
> Richard Kreiss
> GCC Consulting
> 
> 
> 

Richard:

The user just showed me the same error message as noted above except it was
on one of the other two files I mentioned.  However, this time the line
number referenced is a lookup free posting a new record to a detail file.  

I have never used the LOCKED command before.  Your work around makes sense
since most times the user can immediately go back and scan that record.  Of
course this won't help with the lookup free record.  Since 2 out of the 3
files I mentioned are reference files (the third is a detail file I'm
posting brief information to) I wouldn't expect a user to be updating any
records in those files and I don't understand why the user would receive the
error on a non-protected lookup even if another user was looking into that
same record.  Remember they are only assigning data to dummy variables, not
updating or posting records to the lookup file (2 out of the three, the
third is posting data via lookup free).  Very curious.

Don Coleman
Donald G. Coleman, Consultant
402 Andrew Circle
Indiana, PA 15701
dcoleman at dgcreact.com
(724) 349-6302