Can't run reports because file locked?

[Jeff Harrison]

--- Joe Chasan <joe at magnatechonline.com> wrote:

> On Thu, Sep 08, 2005 at 08:34:13AM -0700, Jeff
> Harrison wrote:
> > --- Jeff Harrison <jeffaharrison at yahoo.com> wrote:
> > 
> > [snip]
> > > 
> > > Dan, this behaviour is due to the *file* lock
> that
> > > filepro automatically places on the file when
> you go
> > > into the inquire/update/add program.  This
> behaviour
> > > is as advertised.  You can add a -u to the
> > > dclerk/rclerk command line if you do not want
> this
> > > behaviour.
> > > 
> > 
> > [snip]
> > Oops.  Sorry, you would add the -u to the
> > dreport/rreport line in order to have it ignore
> the
> > clerk file lock.
> > 
> > Jeff Harrison
> > jeffaharrison at yahoo.com
> 
> i *thought* the "-u" told filepro not to *SET* the
> lockfile, which would
> mean he'd want it on the dclerk/rclerk command line,
> not the dreport.
> 
> whether or not he'd want it on the dreport as well
> is another issue.
> if its a non-posting report, he'd probably want it
> on it too, but
> that's not his problem - his problem was that dclerk
> was creating
> the lock, not dreport.
> 
> ...and i second walter's thoughts, i cringe at
> giving regular users access 
> to dpromenu.
> 

No, the -u is only for d/rreport.  It allows users to
run request output with processing even though someone
is running inquire/update/add on the file.  The menu
help only documents is for request output, and I went
ahead and tested this just to make sure this was not
an undocumented clerk feature.  It is not.

I agree too, that you would not normally want to give
a "regular" user access to dpromenu.

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