2009-09-20 - SQL Error back again?

[Donald M. Scheef]

I have been able to post new messages but am unable to edit any of my previous messages.
Has anyone else had similar problems?
Is there anything I can do as a normal participant (not one of the administrators) to avoid or work around this problem?
Don S.

[Mk 1]

I have been able to post new messages but am unable to edit any of my previous messages.
Has anyone else had similar problems?
Is there anything I can do as a normal participant (not one of the administrators) to avoid or work around this problem?

Don (and all):

Here is my best advice for when you get bitten by the SQL Error Log (SQerL) ...

1 ) If you think you are in SQerL season, copy and paste the content of your posting to some scratch location before you hit the SUBMIT button. If you are surprised by a SQerL bite, you can usually still achieve this by hitting the BACK ( <= )button on your browser to return to your posting prior to hitting the SUBMIT button.

Your scratch location can be just about anywhere. For me, I just to a COPY to the scratchpad before I submit, to see if it goes through or not. If it goes through, then I just continue along my merry way. If it does NOT go through, then I open up MS Word and paste my posting into a file, which I save in a TEMP folder (things I can delete without worry later).

2 ) Don't re-submit the posting right away. Please. PLEASE! If you are a bit patient, very often, after seeing the SQL Error Log screen, and convincing yourself that your posting has been obliterated, you will be pleasantly surprised to see that your posting did in fact go through -- it just took a little time. 20 to 30 minutes seems to be enough for most posts to clear, although I think I recall one taking more than an hour. So long as you have your post sequestered away in a safe scratch location, don't sweat it. Go on with whatever else you want to do, and come back in a little while to see if your posting did actually appear, or if it needs to be re-posted.

3 ) Drop a PM to one of your friendly moderators, or directly to GHQ, and mention the SQerL bite. In particular, if you can save the actual error message (the error log) and paste it into your PM (it usually contains referrences to several error code) it can be helfpul. GHQ is pretty quick about getting their tech support folks onto these things, and most SQerL infestations get resolved in one or two business days (if the error log information is made available).

Hope that helps.

(BTW - I deliberately posted, then edited, this message. Trying to test whether I could get a nibble from the SQerL. But alas, I am not SQerL bait today. -Mk 1)