>Gunnar, I havent read this entire thread so dont know if you found a solution. However a possible option is to keep a single ON ERROR assignment but have a public variable (gasp!) which you set / reset / increment / whatever each time the ON ERROR program is called. The ON ERROR routine can then test for the value of this variable and decide what to do.

i tried that, and it seems that if an error occurs within the error trap (called from 'on error') the 'on error' command is ignored for the duration of the error trap and a fox error message is displayed. i even got to the point where i put the testing of datasession availability in a seperate method (set datasession to # - was there an error? - fill array) and the error (which should be triggert) was totaly ignored. i think because the error trap called a sepereate method.