Possible bug: locfile is locked for qualifiers when only main file is locked by user

[John Esak]

Can anyone verify for me the following situation. I know this has been
reported before... but I want to verify that it is truly a bug before I
write all sorts of code around it.

You have a qualifier that is absolutley not locked by anyone. No one in the
qualified file in any program... Yet if you run a script which has:

   ddir filename -k -m that-qualifier

It will fail with a locfile message if someone is in the unqualified main
file, say in *clerk.  This is a serious problem for me. I have a "test"
qualifier for a series of 25 files or so. By running tests in this qualifier
and then quickly clearing the data and re-running tests (after prc changes,
etc.) I can debug things very quickly. My scripts are starting to fail in
the daytime when people are in the unqualified file... (or possibly
*another* qualifier?)  I don't remember the locfile makeup, is their only
one lockbit for _all_ qualifiers? That must be what it is, right?  This is a
drawback that I have never run into before... but it is sure a show stopper
for what I'm trying to do.

--
John Esak
(570) 384-2444

Visit The FP Room www.tinyurl.com/97y9u 24/7

Author of:
The filePro Survivor Series
Video Training For FilePro On CD
See samples at : www.valar.com/training

Publisher of:
The FP Survivor Addendum CD (quarterly)
Learn more: www.valar.com/fpsa