Recent content by KarinV

Thanks. There seems to be another problem. First the LEAVE-trigger is fired. But you got me on the right track. A possible solution is this: In every LEAVE-trigger: IF NOT (VALID-HANDLE(LAST-EVENT:WIDGET-LEAVE) AND VALID-HANDLE(LAST-EVENT:WIDGET-ENTER)) OR SELF <>...

It already is NO-ASSIGN. The problem is that there is one procedure (for all updateable browsers). The row-leave trigger validates and stores the data. Nothing wrong with that, except that the row-leave trigger is fired at unexpected moments. Is there a way to tell if the row-leave is the result...

I am using an updateable browse. When I use another application (to check some data or something like that) and I return to the browse, the row-leave trigger fires, writing a record in the database when I don't want it. I would like to be able to switch windows without my browse being affected...