>Terry,
>
>Ok, let me explain what the problem is and what I expected as a response.
>
>When you open a transaction, once you did tableupdate(.t.,.t.,"MyTable"), you can not use myTable in a separate session (you'll get File is in use error). So, first of all, I wanted to receive a confirmation, if the problem is reproducible. My second question was, if this is an expected behavior by design or it's a bug. And finally, what kind of workarounds could be proposed to solve this problem.
>
>Viv reproduced the problem and I believe his response I can take as this is an expected VFP behavior by design. He also tried to suggest workarounds.
>
>Fabio is thinking, that different setting of TABLEVALIDATE affect this behavior. That's I asked my colleague to test and he told me that there is no difference.

It solicits your colleague to change TABLEVALIDATE, the table it is had to open,
but, of course, you cannot add records because the table's header is in lock.

Practically when tableupdate() is done within a BEGIN TRAN all the locks become
pessimistic.

>However, I think he put this setting in his code and didn't try in the separate VFP session to apply this setting. So, I'm asking >him to re-test.
>
>Unfortunately, I do not see more responses confirming that this behavior is right, so I still have some doubts, because Help does not mention the error we're getting.
>
>Thanks again and sorry for misunderstanding. Perhaps I mistyped my original pseudo-code sample and you concentrated on this instead of the real problem.