dprodir problem with qualifier

[Bruce Easton]

Don Coleman wrote Wednesday, March 18, 2009 3:16 PM:
>
> Bruce Easton wrote Wednesday, March 18, 2009 2:46 PM:
> > To: 'filepro list'
> > Subject: dprodir problem with qualifier
> > 
> > Filepro 5.0.14 on Windows 2003 server.
> > 
> > I searched in filePro's online manual and my saved forum mail (with 
> > 'Directory' and 'ddir' and 'dprodir'), but didn't see anything that 
> > would explain the following behavior (although I vaguely 
> remember some 
> > issue with the Directory program that might be related, so I was 
> > expecting to find
> > something):
> > 
> > Running dprodir, I selected a file, then selected qualifier 
> 'client', 
> > confirmed that it was showing info for that qualifier, then 
> attempted 
> > to remove key and data with option D, then L for 'Delete 
> Format' and 
> > 'Key & Data' respectively.  I got the filepro error:
> > 
> > Not available.
> > Someone else is using it; try again later.
> > 
> > I checked and no *CLERK nor other fp runtime processes showed up 
> > against any file on that system.
> > 
> > So I pressed enter to return and then 'D' and 'M' to clear the 
> > lockfile for qualifier 'client'.  Then tried again to clear 
> > 'keyclient' (with 'D' and
> > 'L') and still the same fp error.
> > 
> > I then cleared (using 'Q', 'D' and 'M' in the directory 
> program) all 
> > of the lockfiles for that file (it has three others, besides 
> > '[NONE]'), and then tried 'D' and 'L' to clear key and data for 
> > qualifier 'client' and, to my surprise, it worked just fine!
> > 
> > In all cases above, use of 'D' and 'M' behaved as expected 
> - that is 
> > there was no feedback from filePro from clearing the 
> particular lockfile.
> > 
> > Does this make any sense and/or has anyone else seen this behavior?
> > 
> > Bruce
> > 
> > 
> > Bruce Easton
> > STN, Inc.
> > 
>
> Bruce:
> 
> I have a client w/ Windows 2003 server & WIN2000 & WIN XP 
> Prof client running fP v5.0.13.  I see this same behavior all 
> the time.  You have to delete all the qualified lock files in 
> order to delete the data in any one of the qualified keys.  I 
> find it easier to do from Windows Explorer (after verifying 
> no one is actually in the file via Manage>Open Files).
> 
> 
> Don Coleman
> Donald G. Coleman, Consultant
> 402 Andrew Circle
> Indiana, PA 15701
> dcoleman at dgcreact.com
> (724) 349-6302
> 

Thanks Don and Richard for the replies.  

I tried to run the same scenario again (having already done it twice) to
make sure it behaved consistently.  Still no users on the system, this time,
after clearing all of the lockfiles for the file via Directory program,
dir's option 'L' did NOT let me clear the key and data (and I should say,
for this qualifier, users do not have access to go into it directly - and I
really do not believe that qualifier has ever been 'in use' during my
testing).  So I manually removed all of the lockfiles for the file and it
then questioned me to clear the key and data for the 'client' qualifier
(which comes up after any error).  

But then, this time, I chose 'N' (to say I changed my mind - don't delete
the key and data) and I got a "Create Process failed() comspec="" error (so
I'll have to have someone look at that problem).  I was able to exit out
normally, but it that is interesting that this behavior seems to be 'normal'
or not surprising to some.  Makes it kind of difficult on a windows system
to have maintenance such as clearing qualified files occur via cgi without
requiring people be out of other data sets of the same file.  Sounds like
safest thing at this point is to not use qualified files under Windows for
such purposes.

Bruce

Bruce Easton
STN, Inc.