>You should test whether TABLEUPDATE() returns an error, then if necessary ROLLBACK the transaction.
>
>Charlie

I have an error routine that'll catch the errors from TableUpdate and any other error for that matter. Since it hasn't kicked in (and i know it works) i'm looking at other causes. I've changed the buffering on a couple of tables (to pessimistic) and things have improved a lot based on just those changes. I'm still running into problems if more than 3 people are doing the exact same thing at the exact same time (my testing guy is getting good at clicking 3 small buttons on three computers at the same time, lol) so the next step for me is to look into more rigorous file/record locking.

---
Jonathan Chan