I have been using using Readonly( ) statements to help with navigation. I am not sure if it is an intended use. The problem I have,  that if I put it in the element (on element exit event) just before the element on which I need to execute Readonly( ) statement to make element readonly so that the cursor would not go in that.  The problem is that the ReadOnly statement does not trigger before the cursor is already in the element that should have been readonly.  If I put the statement in one element before that it would work fine, but it is not always possible to do so. One would imagine that all the statements in the element will complete before the cursor reaches the element.  Am I making any sense here?

I try to avoid using goto and ThrowFocus( ) statements to facilitate use of mouse.

Bharat Naik

Quote:


As I understand, change execution order is applicable only in "On Form Change" event. How would you use that to help in navigation to assure that it would not impede the mouse use?  Bob, would you please elaborate on that?  If there is goto statement in an element and if you click with mouse on any other element on the form, it will be totally ignored and cursor will land where goto statement dictated.

Bharat

Why ReadOnly statement in the element is not executed before the cursor reaches the next element? I guess it will execute if I put it in "Element Immediate Change" event but then it will get to that part of programming with every stroke of the key and that seems like waste of resources. However with conditional statement it will execute only once.

If @Readonly (BP) = 0 then
          {
                  ReadOnly (BP, 1)
             }