At 11:12 AM 21/04/2004 +0200, you wrote:

>Hello!
>
>I try to solve why after a record is inserted to a dataset it is not
>immediately visible when reading it. AutoCommit is true for all my TIBOTable
>components.
>
>In some parts of my application it is necessary to see always the most
>actual content of the datasets. I tried to set caFetchAll for the
>CommitAction property and it seems it helped, but I in fact don't know what
>this value does.
>
>The questions are:
>1. Can caFetchAll solve my problem, won't there be some problem with
>increased network traffic or so?
>2. Is there some other solution for this? (I don't understand why a record
>shouldn't be immediately visible there should be no blocking transactions or
>whatever, I think).

The dataset is only a copy of what is in the database. IBO fools you to
think you are inserting into the database. You're not, of course: IBO
does that for you behind the scenes, by composing an INSERT statement based
on what you entered into the fields of the editing control.

So, after the commit, to see the new database state INCLUDING your new
record, you have to REFRESH the dataset - set CommitAction to caRefresh or
caRefreshKeys.

Helen