Yes, I'm using optimistic buffering on the form. I also have a read-only grid on the first page of the form that provides a search object for the name field.
I noticed that the "ghost" record problem only appears when I edit the name on the same record from 2 different instances of the form at the same time, ie. when there is a data-conflict involving the field that's on the grid on the first page. I suspect it's probably something to do with Table vs. Record buffering since a grid is involved, and the _datachecker class doesn't handle it by itself. The info I have on the class is real sparse, and the sample that ships with MSDN is busted (can't find _table2.vcx).

Rod Poujade



>>Maybe I'm not handling it properly, but does anybody find the Cancel option on the _datachecker FFC object weird? Choosing Cancel on the Conflict MSSGBox seems to whack the index, producing a "ghost" of the record. Any ideas?
>>
>>Rod Poujade
>>McGill University
>>Montreal, QC
>
>Hmm... strange. Did you trace the code? Are you using buffering?
>
>BOb