escaping idle users back to menu

[Fairlight]

Simon--er, no...it was Richard Kreiss--said:
> 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

"Turn off session timeouts."

Problem solved.

> 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.

Sounds like treating the symptoms rather than the disease.  You should
really stop randomly deleting files and fix the cause of their being left
there in the first place.

> 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.

I know people that rebuild auto indexes nightly, whether they need it or
not--simply because they -could- go bad for some mysterious reason.

> 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.

They'd have to implement select() in the *clerk engine--something I've
advocated since 1993, but which has never been felt necessary by TPTB.
Luck with that.

mark->
-- 
Audio panton, cogito singularis.