Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 03 DEC 2003 11:55:29PM Andrew M Matthews wrote:

Does anyone know how to detect if an edit table is in edit mode?

My problem is that users change text in an edit table, and while the edit table is still in edit mode, the users are pressing the F9 key (which is an accelerator key that calls the WRITE event). This results in the data in the cell changing, but the changed event is not firing and so other values in the window are not being updated. (User changes the Qty and the total price is not changing.)

I need some way to stop this from happening as data is being saved incorrectly as values do not match.

Cheers,

Andrew Matthews

iTMS Software


At 14 DEC 2003 05:55PM ps wing wrote:

Is a problem in Arev too.

Had to do "if wc_is% ne wc_is_orig% then @record=wc_is%" to update the actual record.

Cant think of a way to do this in OI at the mo, but good point.


At 15 DEC 2003 07:54AM Don Miller - C3 Inc. wrote:

What I have resorted to is:

On the Read Event, I save the original record in @ORIG. If it's a new record, this will be blank.

On the Write Event, I check the necessary bound elements in the form against the @ORIG data to see if any inconsistencies have developed. This is frequently nessary to do "incremental" updating of bound / related tables. E.G., the user changes the QTY or PRICE in an Edit Table and I have to back out the original data from an Inventory record and then update the new data. This is kind of equivalent to the @OREC construct in AREV which worked fine in these contexts for years. In OI, you can do similar logic in DB_TABLES by checking the POSCHANGED event as well.

While the F9 accelerator key is useful for AREV users, it does require you to take some extra steps at the Write event to make sure that things are getting updated correctly ahead of the actual Write.

Don M.

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/1f02b8f63dc4cc7b85256df2001b0da8.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1