Input Problem

[Dennis Malen]

George,

We will experiment and use the close command although the list has opined on 
that before by indicating it should be unnecessary. We'll try it anyway. It 
can't hurt. It will take two days before it locks up again to report back to 
the list if it does not work.

We are also considering an index corruption problem and are tracking that. 
At some point, we don't know when, the index does not show all the records 
it should. Once we rebuild the auto index the appropriate records are shown. 
This is a small file with only a couple hundred records but with about 9 
auto indexes. It is an important file which is used by about 25 people all 
day. We have not been able to directly relate this to the lock problem.

Thanks,

Dennis Malen
516.479.5912
----- Original Message ----- 
From: "George Simon" <GSimon at americanriverintl.com>
To: "Kenneth Brody" <kenbrody at bestweb.net>; "Dennis Malen" 
<dmalen at malen.com>
Cc: "Filepro_List" <filepro-list at lists.celestial.com>
Sent: Tuesday, April 24, 2007 11:56 AM
Subject: RE: Input Problem



-----Original Message-----
From: filepro-list-bounces+george=worldest.com at lists.celestial.com
[mailto:filepro-list-bounces+george=worldest.com at lists.celestial.com] On
Behalf Of Kenneth Brody
Sent: Tuesday, April 24, 2007 10:34 AM
To: Dennis Malen
Cc: Filepro_List
Subject: Re: Input Problem

Quoting Dennis Malen (Mon, 23 Apr 2007 18:04:07 -0400):

>> Coincidentally, we have been having the same problem on the same
version
>> of filePro. I was reluctant to report it.

Well, it won't get fixed then, will it?

>> The only way we can fix the problem is to reboot the system. We have
to
>> reboot about every two days in order to solve the problem.
[...]

> What, exactly, gets locked up?  When it happens, can you single-step
> the processing and see exactly when/where it locks up?  Perhaps it's
> a protected lookup to a record which is locked?  Run showlock to see
> who has it locked.  I doubt a reboot is really necessary, unless it's
> a bug in the O/S itself.

I've had users reporting similar problems and the only way I've been
able to solve it is by closing every lookup I open.
There _is_ something different in the way that filePro goes about when
releasing a lock.  Not only with my programs but with its own programs.
For example, if you go into define files just to look at the file
layout, without pressing U to Update, and then try to open another
window and go into Inquire, Update, Add for the same file. You will get
an error saying that the Define Files Function is running on this file,
which I don't think was the case prior to this version.
Likewise, in Define Output.  If you go and just bring up a form without
pressing U to Update it and then open another window and attempt to just
bring up the same form, you get a "Permission Denied" error.
It just seems to me that filePro now applies locks sooner and waits at
least 1 keystroke longer to release the lock than before.