Freechain Issue

[Jeff Harrison]

--- On Mon, 8/3/09, Chris Sellitto <sellich at guaranteedreturns.com> wrote:

> From: Chris Sellitto <sellich at guaranteedreturns.com>
> Subject: RE: Freechain Issue
> To: filepro-list at lists.celestial.com
> Date: Monday, August 3, 2009, 10:02 AM
> 
> > -----Original Message-----
> > From:
> filepro-list-bounces+sellich=guaranteedreturns.com at lists.celestial.com
> > [mailto:filepro-list-
> > bounces+sellich=guaranteedreturns.com at lists.celestial.com]
> On Behalf
> Of
> > George
> > Sent: Saturday, August 01, 2009 8:11 AM
> > To: 'Kenneth Brody'; 'Scott Brown'
> > Cc: filepro-list at lists.celestial.com
> > Subject: RE: Freechain Issue
> > 
> > Actually, there is a program called consolenoclose.exe
> that disables
> the x
> > button and removes the close system menu item of all
> console windows
> when
> > they become active. It runs invisible in the
> background.
> > 
> > -----Original Message-----
> > From:
> filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com
> >
> [mailto:filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.c
> om]
> > On Behalf Of Kenneth Brody
> > Sent: Friday, July 31, 2009 8:29 PM
> > To: Scott Brown
> > Cc: filepro-list at lists.celestial.com
> > Subject: Re: Freechain Issue
> > 
> > Scott Brown wrote:
> > >
> > >> Bill Campbell blabbed on about:
> > >>> How do you train Windows to exit
> cleanly?
> > >> Swat it on the nose with a rolled up printout
> when it leaves a
> minidump
> > on
> > >> your hard drive.  :)
> > >
> > > But what if it bytes you when you swat it? 
> :)
> > 
> > I've got a "format c:", and I'm not afraid to use it!
> > 
> > --
> > Kenneth Brody
> 
> George,
> 
> Good program.  I just tried it, and it works
> well.  I will see if it
> helps with our issues with freechains.
> 
> Christopher Sellitto

Perhaps it will help, but don't underestimate a determined user's ability to screw up your system.  They will find a way.  (Task Manager comes to mind - or Reset!)

You may want to add some logging to figure out which users are doing this and then get with them and find out why.  Also, you can attempt to educate them on this.

It may even be that they are doing this because of a bug or locking issue.  For example, if you lock a record in your programming and then do a popup or input - it is possible for an idle user to lock that record indefinitely.   If this is the case, then you should fix your code to minimize these types of issues.

Good Luck.

Jeff Harrison
jeffaharrison at yahoo.com