Hi Marcia,

Another testimonial to the joys of table buffering, discovered around the midnight hour last night (life, what life?)

Ive been struggling with a wizard generated form that uses an updatable local view as the data source and a primary key with a default value that calls a routine to generate the next key (.value = nextcd('maincd').

With row buffering I kept getting update conflicts each time I attempted to append a new record, or the message that the view was 'not found' when I attempted to exit the form. I believe due to the view record being updated to the base table before the key could be assigned, leaving the two out of sync.

Table buffering seemed to fix this problem. I believe this is due to the view dumping all updates to the base table at once.

I suppose the downside with table buffering, if I understand correctly, is that if the update bombs a batch of transactions could potentially be lost. Has this been a problem for you?

Regards,

Todd