Search results

This may seem an unothodox approach but it seems to work. Make your second smart browser contain a work-table like the table in your first. Set the external table in the second browse, to be the table in the first. Freeform your query in the second browse to execute on your work-table (...

I am currently having a real problem with transactions being extended beyond the scope of the trigger in which they are contained. An example of the trigger code would be: DO: FIND numbers EXCLUSIVE-LOCK WHERE numbers.class = "L" NO-ERROR. IF AVAILABLE numbers THEN DO: CREATE...