>Upon further testing the crux of the problem appears to be that the code itself is within an "on error" routine. When running the code, or similiar code supplied by Nayda, outside of the error handler, the 1540 error is trapped. But within an on error routine it insists on giving a c/s/i message before doing the active error trapping to catdh error 1540.
>
>Thanks to both of you.

That would be correct. You cannot trap further errors within an error handler. That code must be perfect! < g >