>>FYI, I assume you are using the identity clause in SQL server to
>>generate your unique numbers,
>
>That's correct.
>
>I guess I don't really need to REQUERY that identity field in my view (it takes too long)
>
>But why would TABLEUPDATE(.T.) return ".F." when I can tell that the INSERT has happened ok because the new record shows up in the web page or by querying with SQL Query?

I've never had that problem. Have you tried it with Optimistic Row buffering (3)? I think I read somewhere that SQL Server doesn't like table level locking, I find that hard to believe, but....

HTH,
Scot.