Yeah, I thought of that. I was just trying to avoid doing that in 39 places. :) Actually, possibly more than that now because I discovered there are more calls than I thought.
I'm going to do a little more research and see if I can't narrow down the scope a bit.
Thanks,
Michelle
>Michelle,
>
>Another approach would be to add a parameter to the procedure, and then pass a different number for each specific location in the suspect routine.
>
>Ensure that the value is in scope for the error routine. IF TYPE ("nLocation") <> "U" then report it.
>
>Not sure if this is feasible, but it would be simpler than logging gobs of stuff.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only