I'm going to hazard a guess as to what you are doing: Each client has its own record in Status, and only updates its own record in the Status cursor. But the VStatus view is used to update other client's records in the same table. Correct?

If I'm wrong, please let me know the view definition, and what records are being updated in the vstatus workarea.

>I have an compiled vfp7 app running over citrix/WTS using wyse thin clients, with my exe and database on a netware 4.11 server. About 30 users. When they click "save" the following code is run...
>
>(There is a table "status" and a view "vstatus", both are buffered mode 5)
>
>

>set reprocess to 30 seconds
>replace status.ncounter with status.ncounter + 1 in status
>begin transaction
>if tableupdate(.t.,.t.,'vstatus') and tableupdate(.t.,.t.,'status') then
>     end transaction
>else
>     =messagebox('Error saving data',0,'Error')
>     rollback
>endif
>

>
>The app is freezing up when the second tableupdate occurs. A look at the
>netware server shows status.dbf with a "locked" status for maybe 5 users. I have to kill the connections till only one user is left and then they unfreeze and continue on. I thought that if the record was locked for more than 30 seconds (which it shouldn't be with that short transaction) the other users would fail the tableupdate and get an error message. This isn't happening. It's almost as if the reprocess is infinite. Any tips?