Lockfile question

[Don Coleman]

> -----Original Message-----
> From: Jeff Harrison [mailto:jeffaharrison at yahoo.com]
> Sent: Monday, September 18, 2006 5:56 PM
> To: Don Coleman; 'filePro'
> Subject: RE: Lockfile question
> 
> --- Don Coleman <dcoleman at dgcreact.com> wrote:
> (Top posting fixed)
> 
> > > -----Original Message-----
> > > From: Jeff Harrison
> > [mailto:jeffaharrison at yahoo.com]
> > > Sent: Friday, September 15, 2006 5:53 PM
> > > To: Don Coleman; 'filePro'
> > > Subject: Re: Lockfile question
> > >
> > > --- Don Coleman <dcoleman at dgcreact.com> wrote:
> > >
> > > > 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.
> > > >
> > >
> > > Don, is that the complete error message?  It
> > sounds to
> > > me like there should be something else.
> > >
> 
> > Jeff:
> >
> > I believe that it is.  I will try to confirm today.
> > There is a second part
> > but it refers to fP not being able to open the
> > errmsg file.
> 
> If there is a second part (that you did not mention
> previously) then that was NOT the complete error
> message! :-)
> 
> If filepro can't open the error message file, then I
> would hazard a guess that your problem has to do with
> and environment limit on either the number of files or
> buffers, or something like that.  I'm not windows
> expert, but I know that this is configurable for each
> command prompt - the number of files and buffers that
> you can open at one time.
> 
> I hope this helps.
> 
> 
> Jeff Harrison
> jeffaharrison at yahoo.com
> 
> Author of JHExport and JHImport.  The easiest and
> fastest ways to generate code for filePro exports and imports.
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com


Jeff:

You may be on to something here.  I normally have in my startup environment
(batch file) 
SET FILES=80
SET PFFILES=60

I just noticed this is omitted from the .bat file being used here.  Is there
any limit as to what the FILES and PFFILES environment can be set to?
There are many lookups and several call routines in this app so am I causing
any problems by setting both FILES & PFFILES to either 100 or 200?  The
clients where this application is used are dedicated to this application and
are only rarely used for anything else.  Or should I start with my normal
environment (FILES=80, PFFILES=60) and increase incrementally as needed
until the error is eliminated?

Any Windows experts care to weigh in on this?  Ken, Bob H., Richard K.,
Mitch, etc?

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