>>A couple times today I've hit an error. The second one for sure was when submitting an update to a previously created message. I don't think UT will allow the tags so I'll encase everything in PRE.
>
>I cannot reproduce that. If you have a pattern to simulate that, you may send that to me by email.
It's (obviously) intermittent. For sure, the second one was during a message update, the first one may have been as well. This seems to be borne out by some strings in the detailed error message.
Also, since your complete switch to SQL Server the UT has been much snappier. During both of the errors I received, I noticed there was quite a long pause (est. 8 - 10 seconds) when nothing happened, then the errors came up. Most other actions (including some other successful message updates) seem to complete successfully in less than a second.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up