What if.....
1. I create a generic user that no one has ready access to.
2. In the database I give this user all access to _DML_ tables.
3. In the database I create a procedure that posts a update
record in DML$IBOCACHE (much like the DML$IBOCACHE trigger)
4. I can then call this procedure from any app.

Then this will, in effect, simulate another user updating the
current _live_ record that the user is working with. ????

Steve Fields

Steve Fields wrote:

>
> Helen, I am currently setting it to tiReadCommitted because
> somewhere, in this forum, I read that I need to set
> read committed and do not use autocommit (server or local).
> I forget why now, but it was what I needed as a basic
> setting(s) 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.
> This is for a basic invoice/lineitem type of system,
> with twists relevant to our situation. I would make the
> changes in the background to the line items and the base
> totals, etc with a tib_cursor or a tib_dsql, (whatever it
> takes) but needed the values to update immediately on posting
> the lineitem changes. I am using all of the DML settings as
> true for each dataset involved (TIB_Queries and a few
> tib_cursors).
>
> Steve Fields
>