>>My users are having a bizarre problem that only recently began happening. A call to "Tableupdate()" with
>>all rows (Optimistic table buffering is enabled) and
>>no force (users are essentially appending records to
>>table) freezes their system. Behind the scenes, it
>>seems like only some of the records are copied, and
>>then nothing...no errors or anything. I do not
>>have any triggers on this table, and hardly any
>>data validation.
>>
>>Anyone have any ideas?
>>
>>Thanks,
>>Laura
>
>May be you have primary/candidate tags and new records offend them.


This would normally generate an error message like
"Primary index is not unique..." or some such thing.
And, furthermore, there is no primary index on this
table.

Any other ideas? I am going to be wrapping this update
into transactions, however, I am still very curious as to
how this could happen, and why only some records get updated.