escaping idle users back to menu

[Kenneth Brody]

Can you please get an e-mail program that's able to properly quote when 
replying?

On 2/12/2011 9:47 PM, Rkreiss at verizon.net] wrote:
> From: Kenneth Brody<kenbrody at spamcop.net>
[...]
>> One other problem arose which we just discovered and fp support does not
>> understand why this should be a problem.  On the terminal server machine,
>> c:\fptemp is where fptmp is set.
>
> What does PFTMP have to do with record locks?
>
> Nothing to do with record locks except that after deleting the 1550 or so files in fptemp, users were able to enter comments.  Before these files were deleted, when a user tried to enter a comment, the session froze.

How do the user "enter a comment"?  What program are they using, and how far 
do they get before they run into a problem?  And what, exactly happens at 
that point?

>> Over the last 5 years for one reason or
>> another, there were somewhere between 1500 and 1600 files left in this
>> directory.
>
> While that may affect filesystem performance, it shouldn't have any other
> effect on filePro.
>
> See my comment above.  Files deleted, program works.

DDW.  :-)

[...]
>>   A task has been added to run at 1AM on
>> Sunday when no one will be in the system.
>>
>> As for rebuilding auto indexes, it makes sense if an index has gone bad for
>> some reason and all work has to stop to rebuild the index Especially if the
>> work day runs from 8:30 AM EST to 9PM PST.
>
> Do you have any reason to believe that an index has gone bad?
>
> Yes, filePro reports that automatic index X needs to be rebuilt.  This entails getting 10 people in the office off and 1 - 20 remote usersd off.  That means all work stops.

I suppose with all of the session killing that's going on, things may get 
corrupted, but from what you have described, nothing would cause a corrupted 
index in those scenarios.

> Now you may be correct about the file names. By deleting any orphan files once a week, they should not run into this situation again.  This may also solve the index problem as most of the time it was on market-memo.

Unless it's something in filePro that would be using that directory, such as 
running a report, then there's no reason why it would have any effect on 
filePro.

Note that you still haven't described what the users are actually doing when 
they have a problem, beyond generic descriptions like "adding a comment".

>> One other thing, the program adding records to the market_memo file has been
>> changed from using a popup update to the file, to popup update - and using
>> dummy fields to get the comment being added.  Only when the memo info has
>> been confirmed will it get posted.  This removes the chance that a session
>> will be left open while someone had a record locked in the marketing file
>> and in the market_memo file.
>
> What about the record that they're sitting on?
>
> To afd a comment, @key is used.

But they're updating the record they're sitting on, even if that's not in 
the marketing file.

>  They are not directly in the marketing record (update mode);
> As such, if the session stops or crashes, nothing is lost from the record.
>
> In this application, most update are done using @key and either poping up a screen or updaing one field with input popup nn.
>
> Browse lookups also make usde of @bk to update related information.
[...]

-- 
Kenneth Brody