>>So the solution should be to not set procedure to Somefunction and keep it unknown at design time.
>
>Works. It happens after some testing, when set("Procedure") still keeps the code available (but the tables aren't open and the code expects them). I'll just add another line to my clean-up-after-testing routine.

CLEAR PROGRAM after removing it from SET("PROCEDURE") should help.

Glad it works for you.

Bye, Olaf.