Marcus
I think you're correct... what you're seeing is most likely not related to MM.

Did you check v_teiausbaubybeweg after the requery to be sure that you picked up the latest data from the save in the other datasession? I'm suspecting that may be causing your problem.

---J

>Hello Jason,
>
>thanks for your answer. Actually I am shure that this problem is not relating to MM because a plain Tableupdate() also causes the same error.
>
>...Checking Requery() Returns - they are OK.
>
>Anyone else an idea ?
>I am still falling over that problem and I am running out of ideas. I modified my testcode a bit (see below) and CURVAL() == OLDVAL() for all fields! (The messagebox never appears)
>
>But I still get the Tableupdate() = .F. with error 1585.
>Is there any known VFP issue with locking probs in Private datasessions ?
>I am using the same view in about 5 Data sessions.
>
>Still looking for all ideas
>
>Marcus
>
>>>

>>>ACTIVATE SCREEN
>>>SELECT "v_teiausbaubybeweg"
>>>IF TABLEUPDATE(.T.) = .F.
>>>   AFIELDS(laField)
>>>   FOR lnLv = 1 TO 16
>>>         ? OLDVAL(laField[lnLv,1])
>>>         ? curVAL(laField[lnLv,1])
>>>         ? EVALUATE(laField[lnLv,1])
>>>         IF NOT (OLDVAL(laField[lnLv,1]) == curVAL(laField[lnLv,1]))
>>>          MESSAGEBOX("Got the Error"+laField[lnLv,1])
>>>         ENDIF
>>>   ENDFOR
>>>ENDIF
>>>