Odd error

Jeff Harrison jeffaharrison at yahoo.com
Tue Dec 18 06:59:09 PST 2007


--- Doug Luurs <doug.luurs at gmail.com> wrote:

> In my 25+ years of programming in filepro, I have
> never seen this one ..
> Anyone every see it, or have
> an idea what caused it ?
> 
> User was going into IUA (dclerk) using a normal
> Index selection (Index A -
> One field, 6 characters-Nothing fancy)
> *
> Fatal error
> /appl/filepro/payables/index.A: Deadlock situation
> detected / avoided.
> 
> screen ,1
> 
> *Program worked fine once we hit ENTER and tried the
> same lookup again.
> *
> *I am thinking it the program was having one of
> those senior moments.
> (Similar to us old farts)*
> *

I have seen this before - I'm not sure where -
probably this very mailing list.  My understanding of
a deadlock is that two processes are vying for the the
same lock or set of locks on the same record at the
same time.  Usually filepro will just allow the first
process to create the lock(s), and the second will get
the "someone updating" message.  For whatever reason,
it sounds like your process thought that it should be
able to do it's locks, but so did another process.

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHExport and JHImport.  The fastest and
easiest ways to generate filepro exports and imports. 


      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping


More information about the Filepro-list mailing list