>Ed may have the answer in the buffering solution he offered. I've never seen a case, though, where buffering prevented you from seeing a new record in the cursor you added the record to, though. You just can't see it in other data session, or, in the case of a view when the view is buffered, you can't see the new record in the source table.

Barbara,

I've specifically seen it when a double-buffered view added a record, and an INDEXSEEK() was issued against the base table, or another view of the base table, without that TABLEUPDATE() being applied. Realizing that the index file is not updated until the buffer is committed to the physical store here is the key; in the double-buffer. single TABLEUPDATE() model, the results of the change to the view are committed to the buffer of the underlying table; until that buffer is committed to the underlying table itself, it won't register as a hit on the index.