>Hi Ray,
>
>>I'm getting TABLEUPDATE() failures when two or more users simultaneously attempt to enter, then save, separate new client records
>
>What does AERROR() report as the reason the for the update failure? Are you generating duplicate keys?

Possibly. This is a bear to debug because I have to do it at the client site via Terminal Services in a runtime-only evironment--and with another recruit coordinated via telephone to generate simultaneous entries. I'm using Doug Hennig's SFLOGGER class to output debug info to a text file. So...I just got last night my first AERROR information, and the error is, ta da, "uniqueness violated." It appears to be occuring in just one table of several that are updated with the addition of a new client. I'm investigating further....

I still don't understand, however, why this would occur in a TS session but not in a traditional client/server environment????