In addition to what Josh posted...you should be checking the return value of TABLEUPDATE in case it fails. Also, if use the alias parameter of tableupdate then you don't need to select (takes time to select a work area, saves code, too).

Just my .02 US

>On tables that have OPT ROW BUFFERING (i.e. #3 set in DATA ENVIRONMENT), should TABLEUPDATE(.T.) cause an error when when two users have changed data in the same table at the same time. 'Cause I thought it was supposed to!
>
>I have several tables open at once on a given form. Before my SKIP+1 code I have:
>
>< SELECT A
>< TABLEUPDATE(.T.)
...snip