escaping idle users back to menu

[Richard Kreiss]

-----Original Message-----
From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
[mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
Behalf Of Fairlight
Sent: Friday, February 11, 2011 8:24 PM
To: FilePro Mailing List
Subject: Re: escaping idle users back to menu

Simon--er, no...it was Rkreiss at verizon.net]--said:
> filePro is fairly robust.  I have found tht it takes a lot to mess up a
file.  

Which is why you're always rebuilding indexes, right?

Although I think half the people that rebuild indexes regularly don't know
what they're doing and that you're not supposed to have to--they do it out
of either paranoia or habit.

Mark,

The problem my client has is that they have many employees working remotely
through terminal server.  As they are working at client sites, they
sometimes get distracted and their session times out and disconnects.  In
and of itself, this is not a problem.  However if they are in update mode,
this will lock the file and create other problems with tasks scheduled to
run at night.  Their disconnected session is then logged off.

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.  Over the last 5 years for one reason or
another, there were somewhere between 1500 and 1600 files left in this
directory.  The other day, every time someone tried to access the
market_memo file, the system locked up and the session had to be closed by
clicking on the <X> in the window.  After these files were cleared out, the
programs have worked properly.  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.

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.

One other point, all of the employees are being advised on the proper method
of exiting from the filePro app and they are being told to at least return
to their menu when they will be away or not using the system for more then
10 minutes.

Richard

PS: Still wish we had a way to exit a record that is being updated after NN
minutes of idle time.  Granted this becomes a messy proposition as to what
to do, but that is the programmer's responsibility to insure as clean an
exit as possible.