I probably need to force taking time to research all of
the documentation for IBO, etc. But I am not allowed
to look long before I have to develope something else.

Also in my particular instance I found that DML caching
only executes from outside the current user's connection...

Steve Fields

>
> Helen Borrie wrote:
> > Erm...no.
> > In documentation we loosely use the term "user" when we mean "connection"
> > and, sometimes, "transaction" (or both). A user is only meaningful in
> > terms of a connection - so to do any work, your phantom user would (a) have
> > to be connected and b) have some way to know that an application wanted it
> > to update something. In a sense, DMLCaching gives you what you describe,
> > without a "different" user being involved, since it involves database events.
> >
> > >I was under the impression that to commit it
> > > > would close the datasets relating to the database and
> > > > would therefore _lose_ the record I was letting the user
> > > > view.
> >