I recently built a procedure for interactive selection, started by trigger on the screen, in order to force the user to restrict his/her selection before loading any data.
This is because it would otherwise generate too big reports.
So in the procedure there are several interactive selection steps, on different dimensions. It works quite well in the normal case.
BUT (as always) : if the user cancels a selection, then the procedure stops, and the layout starts refreshing anyway (with a very big data space).
Does anyone have an idea how to manage that ?