Deadlock situation

[Jose Lerebours]

As posted:

> >       Then: lookup apen = mropenitems  k=ke   i=F  -nx
> >   4  -------   -   -
> 
> Make your lookups -nxp when changing data in the lookup file.
> 
> 
> >       Then: lookup mrinvmaster  k=4    i=A  -nx
> > 
> >   -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -    
> > -   -
> 
> Same here.  Always use -nxp when changing data.
> 
> There is nothing here that would seem to cause a deadlock situation 
> but adding the -nxp may give you more information if something ends up 
> waiting for something that was previously locked.
> 

If this does not help, try:
(1) Copy mropenitems/key and mrinvmaster/key to a ~/keyorig
(2) Zap original key files using ddir or ? off the fp menu
(3) Run processing to copy records from ~/keyorig back to ~/key
(4) Run your process again

You might want to want to create a logging file where you can log
your progress and then go back to this file to identify which record you last
updated successfully or which you were attempting to update when the problem
occurred.

There is that chance that you just have a bad key segment or even an index.

Also, isn't there a lock() function or something in filePro that would attempt
to lock the record and tell you if successful?  Use that as well ...

Good luck!


--
Jose Lerebours
http://www.fpgroups.com
954-559-7186
filePro + PHP Solution Developer