I am using RaiseError() to display various messages in a script so I can know where it is as far as the execution. This is a very big script. I found out that after a while, such as 20 minutes, and about 400 lines of display, the display has stopped. This is not even a big command being executed. The portion of that script where this situation happens is executed in fractions of a second. So, I believe this is because the script is too big or that near the end, it reaches a section that it has to index a lot of big indexes. It would then seem that RaiseError() is caching the commands and not displaying them. Is there a flush architecture which applies to the RaiseError() command which might explain this?