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 04 OCT 2002 04:20:09AM Peter Kassinski wrote:

I want to implement my own program code for such events as "insert" or "delete" buttons during editing data in "edit table" control.

I can write event holders for Deleterow and Insertrow events by I also want to suppress system actions of adding and deleting rows.

What is the method would help me to resolve that problem?

Thank you.


At 04 OCT 2002 04:46AM Oystein Reigem wrote:

Peter,

One workaround that's been posted here a few times is to let the handler undo the action of the user by immediately inserting the deleted line again and vice versa. The procedure is very straightforward. I believe you will find it by searching for

"edit table" and insert and insertrow and delete and deleterow

But the proper way to do it is to tick the Protected box in the More dialog of the Edit Tables Properties dialog. As you surely know one can protect agains user changes on a columnar basis by ticking Protected in the Edit Tables Properties dialog, but this particular Protected thing in the More dialog is there to protect against user inserts and deletes.

So why the workaround? (I have posted it myself but then I wasn't properly aware of the More Protected option.) Perhaps for cases where you change between allowing and not allowing inserts/deletes.

- Oystein -


At 04 OCT 2002 04:50AM Peter Kassinski wrote:

Thank you.


At 04 OCT 2002 08:27AM Don Miller - C3 Inc. wrote:

Another good reason to handle insert/delete rows in a table with buttons / dialog boxes is where there are inter-related elements which must be accounted for. For example, when a table row is to be deleted, an element within the table (but not visible) has to be checked to see if this row has been added to another table (e.g., the record has been saved). If so, then the post process logic is quite different that when the row has just been inserted but not processed. Likewise, the inter-relationships of elements within a row are much more easily handled within a dialog box than within a table itself. Therefore, for the most part, I place buttons above the table that allow for Insert / Delete / Change. I also allow a double click on a row in the table to trigger the Change logic.

Don Miller

C3 Inc.

View this thread on the forum...

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