>It looks like I can use ERROR <tiErrNum>, <tcMessage> -- but are there any
>gotchas with this approach?

Watch those brackets, Jeff. :-)

The only problem I've experienced with this is that when you drop into the debugger, you're at the ERROR statement, rather than the line that caused the error. A Skip or two (or checking the Call Stack) fixes this, but it's still a bit of a pain, IMHO....