Input Problem

[Dennis Malen]

Ken,

Once the lock occurs again I will use the debug program. That won't happen 
for another day or two. In addition, there would be no one else going into 
the same record to lock the record unless the use of the auto index scans 
all records and hits the currently viewed record which is an impossibility. 
So even if we use the -p there should not be anyone going into the same 
record to keep them out.

Dennis Malen
516.479.5912
----- Original Message ----- 
From: "Kenneth Brody" <kenbrody at bestweb.net>
To: "Henry Melancon" <hemelancon at gifinc.com>
Cc: "Filepro_List" <filepro-list at lists.celestial.com>
Sent: Tuesday, April 24, 2007 4:25 PM
Subject: RE: Input Problem


> Quoting Henry Melancon (Tue, 24 Apr 2007 15:16:31 -0500):
>
>> What is happening in my system is that the first person is entering data
>> successfully, while a second or third individual tries to saves a record
>> unsuccessfully.  They press the ESC key, the cursor disappears and
>> nothing happens.  You cannot CTRL-C to leave the record.  I think if you
>> wait long enough it will eventually save the record and continue.  I had
>> IT reboot the server at noon and everything seems to be running faster
>> and as it should.  Thanks to all who suggested the reboot.  Does anyone
>> have any ideas as to why this maybe happening?
> [...]
>
> Turn the debugger on and see which line of processing is causing it to
> freeze.  Most likely, you are doing a protected lookup to a record
> which is locked by someone else.
>
> --
> KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
> http://www.hvcomputer.com
> http://www.fileProPlus.com
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>
>