Disabling DBLCLK event in EDITTABLES (OpenInsight Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://www.revelation.com/|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]]


==== Disabling DBLCLK event in EDITTABLES (OpenInsight Specific) ====
=== At 26 JAN 2000 03:45:03PM Robert Lee wrote: ===
 
{{tag>"OpenInsight Specific"}}
 
<QUOTE>
As part of our security system, I am using the following approach to disable edittables at runtime.



*Stop the user from being able to press insert / delete

New.Style=bitand(Style, bitnot(4))

x=Set_Property(DCtrlMap[i], 'STYLE', New.Style)

*Disable each column

ColStyle=BitOr(ColStyle,8)

OldStyle=Send_Message(CtrlMap[i],'COLSTYLE',j,ColStyle)



This way the user can still use the scroll bar but can't change the data or insert/delete lines.



BUT they can double click, bring up a popup, and the selection gets returned into the edittable!!



How can this be stopped for our "read only" users??
</QUOTE>
----

=== At 26 JAN 2000 03:49PM Tony Marler @ Prosolve  Software wrote:  ===

<QUOTE>Robert



Its getting late here! but can you just put some code in the event to not call popup if they are read only users. Either instead of or prior to the quickevent (using RETURN 0) if that is what you are using.



Tony

</QUOTE>

----

=== At 27 JAN 2000 03:09PM Robert Lee wrote:  ===

<QUOTE>Tony

Not that simple.  The security system is used system-wide with many dozens of forms and countless edittables involved.  I was hoping for an approach where I could take a standard edittable with a double-click event that may have script or a popup and disable it.  Five essential elements I am looking for with edittables.

1. Read but not change data. (Done)

2. Can't add/delete lines. (Done)

3. Can scroll (Done)

4. Can't activate especially DBLCLK events. (Help!)

5. Handle the above without code required in every single edittable. (Done - except 4)



A challenge for those genius types out there!



All other controls seem to be under control at this stage.

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=4525CA06E68F8A98852568720071FCFC|View this thread on the  forum...]]