Larry,

Ok I see, you're trying to fake out an ON ERROR type of operation.

One design approach I would probably investigate would be to encapsulate the entire SQLExec stuff into an object. Perhaps with a structure such that the SQLExec that gets executed is created by setting properties of this object and then calling a method that builds and executes the command. This way, if an error occurs the object's properties could be investigated to find out what the context was without the assign method needing to know the line of code for the SQLExec. Essentially it would always be the same line of code.