Hi,

I am sending this message on behalf of a friend of mine (Moshe, for those who know him).

He apparently has found a bug in VFP 9 related to the UNLOCK command. Please, see the code below:

procedure teste

*
* This procedure shows a bug at Vfp9 that occurs with multilock\
* and a table open more than once with AGAIN clause.
*

clear
set multilocks on
close databases all

*
* Here is our teste table.
*
create table teste ( ;
   code1  n(5) ,;
   field2 n(5) )

use teste shared
append blank
repl code1  with 1
repl field2 with 0
append blank
repl code1  with 2
repl field2 with 0

*
* Now we lock for the second record.
*
goto 2
rlock() && Here the Second record is locked.

*
* Now we open again our table teste as "teste_again"
*
use teste alias teste_again in 0 again
sele teste_again
*
* Now we lock for the first record.
*
goto 1

rlock() && Here the First record is locked.
repl field2 with 20 && It's only a field to receive a change.

*
* And now... When we unlock this last record the vfp hangs.
*
unlock && BUG - 100% of CPU usage

*
* If we close the table using (CLOSE TABLE) or (USE) it works.
* But if we try to unlock the record vfp hangs...
*

return

Please, if anyone has any comment about this, I will ge glad to get it and forward to him.

Thanks in advance