I think what Jim meant is you should have contention handling in your update logic that will resolve conflicts regardless of who the two users are (even if they are the same user). The issue is really the same whether it's two different people hitting the record at once or just one person.

>In our particular case, we have the possibility of a user on the workstation running 2 different EXE where the user being on the same exact record in both programs. (unusual but we see it happen). The first program is going to write changes to field1 based on a field2 value and the second program writes to field2 based on field1 value.
>
>if the second EXE writes first, no problem. But if 1st EXE writes, then we get an issue when second EXE writes. I need to make sure that the 1st EXE does not write if 2nd EXE has that form open.
>
>
>
>>I am not sure how you would do what you are asking, but if your forms are designed to be multiuser then there should not be any problem with the two being run at once. The multiuser conflict resolution code will handle any difficulty that might come up.