Subject | Either Grid shows old value & allows post of new with no warning (tiCommit) or cannot see new value (tiConcurrency) |
---|---|
Author | Raymond Kennington |
Post date | 2003-07-31T19:40:50Z |
With tiCommitted the Grid
shows and old value that has been changed and committed by another
allows post of new with no warning
With tiConcurrency the Grid
does not allow refresh of new values provided by another
cannot update
What do I have to do to have:
Edit a changed field causes a PreviousValueChanged message
and
Allows refreshing of the row?
I have separate transactions for each query.
With a single user and one application, is it necessary to also have separate
connection components on the form for each query?
Does using CommitRetaining cause the inability of tiConcurrency edits to not
be visible to another user?
Why doesn't a tiCommitted change using CommitRetaining by one user not cause a
RecordVersionChanged message by a 2nd user when changing the value in the
field?
--
Raymond Kennington
Programming Solutions
TeamW2W (InfoPower)
shows and old value that has been changed and committed by another
allows post of new with no warning
With tiConcurrency the Grid
does not allow refresh of new values provided by another
cannot update
What do I have to do to have:
Edit a changed field causes a PreviousValueChanged message
and
Allows refreshing of the row?
I have separate transactions for each query.
With a single user and one application, is it necessary to also have separate
connection components on the form for each query?
Does using CommitRetaining cause the inability of tiConcurrency edits to not
be visible to another user?
Why doesn't a tiCommitted change using CommitRetaining by one user not cause a
RecordVersionChanged message by a 2nd user when changing the value in the
field?
--
Raymond Kennington
Programming Solutions
TeamW2W (InfoPower)