Can't run reports because file locked?

Joe Chasan joe at magnatechonline.com
Thu Sep 8 08:43:33 PDT 2005


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.

--- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ---
-Joe Chasan-                      Magnatech Business Systems, Inc.
joe at magnatechonline.com           Hicksville, NY - USA
http://www.MagnatechOnline.com    Tel.(516) 931-4444/Fax.(516) 931-1264


More information about the Filepro-list mailing list