I'd personally consider this a defect. I wouldn't be surprised if somehow the ampersand in the password isn't getting escaped properly somewhere in the XML, but that's just a WAG. Even if it's not something that can be fixed (odbc limitation?), a better error description would be good. Google definitely isn't a help, but at least your blog post comes up near the top...<div>
<br></div><div>Bob&Doug? Take off eh! :)<br><div><br></div><div>Jason</div><div><br><div><div class="gmail_quote">On 6 April 2010 20:01, Warren Medernach wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Oh you know it Jason, extremely frustrating… </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I did think about submitting it as a defect, but then I thought is
it really a defect? </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">After reading up a bit on SS password policies, it does state
that non-alphanumeric characters such as: exclamation point (!), dollar sign
($), number sign (#), or percent (%) are valid, it just doesn’t
specifically say that an ampersand (&) is invalid. </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">So, having said all of that… it would have been nice if MG
provided a more description error message, but the question remains, is this a
defect? I can definitely submit a defect, if you feel it is.</span></p></div></div></blockquote></div></div></div></div>