Hi Vladimir,

This form was originally written by my colleague, so I didn't want to dig deep into it. Yesterday I tried different ideas to make it work, but nothing helped. So, I abandon the relationship idea alltogether and was finally able to make it work by using: (got this tip from this forum in one of Vlad's messages)

set key to range iMethodID, iMethodID in ValCalls
lnRecno = recno('ValCalls')
if between(m.lnRecno, 1,reccount('ValCalls')
   goto m.lnRecno in ValCalls
endif

This code seems to solve my problem, which is really weird and very annoying. I spent half of the day yesterday and was quite depressed until I solved it.

Also it was a great help to read funny jokes in Chatter section... This really made my day!

>Hello Nadia
>Did you use any relations between these tables, if so, the problems can be.
>For example, let grid allowaddnew =.t. and one of the columns is from related table.
>If we have few records in the main table and press down arrow ( add record )
>this record will show reference from previous record, just we did set the key for reference. I used relations in 1997 for strings of trade papers ( goods with numbers and price descriptions) and refused from this idea to use related tables. I always founded some strange behaviour, similar to described by you , when did new record , just without allownew. One columns for related table has shown for second or so wrong reference. For long time after it I used other technic, I did find in Pinter letters .
>I use query joining related tables for key from the main table, and make it not read only by -use dbf('query') again in 0
>, makes my own updates back and show this query ( or queries ) in these grids. This works for me perfect in 50-60 forms of different tasks.
>Vladimir