<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlserver.ro/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Database APIs</title><link>http://sqlserver.ro/forums/43/ShowForum.aspx</link><description>ADO, ADO .NET, ODBC, OLE DB, DB-Library</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>Re: ado problems</title><link>http://sqlserver.ro/forums/thread/1301.aspx</link><pubDate>Mon, 11 Dec 2006 12:54:28 GMT</pubDate><guid isPermaLink="false">963f3a18-65dd-4aad-905c-b785cfe1d7c7:1301</guid><dc:creator>crestinul</dc:creator><slash:comments>0</slash:comments><comments>http://sqlserver.ro/forums/thread/1301.aspx</comments><wfw:commentRss>http://sqlserver.ro/forums/commentrss.aspx?SectionID=43&amp;PostID=1301</wfw:commentRss><description>merci.A mers</description></item><item><title>Re: ado problems</title><link>http://sqlserver.ro/forums/thread/1300.aspx</link><pubDate>Mon, 11 Dec 2006 12:15:32 GMT</pubDate><guid isPermaLink="false">963f3a18-65dd-4aad-905c-b785cfe1d7c7:1300</guid><dc:creator>rsocol</dc:creator><slash:comments>0</slash:comments><comments>http://sqlserver.ro/forums/thread/1300.aspx</comments><wfw:commentRss>http://sqlserver.ro/forums/commentrss.aspx?SectionID=43&amp;PostID=1300</wfw:commentRss><description>&lt;p&gt;Bănuiesc că atunci c&amp;acirc;nd rulezi procedura din Query Analizer, obţii şi nişte mesaje cu &amp;quot;n row(s) affected&amp;quot;. Dacă e aşa, atunci acele mesaje pot să &amp;icirc;ncurce error handling-ul din ADO, care s-ar declanşa doar atunci c&amp;acirc;nd apelezi .NextRecordset pentru a prelucra toate răspunsurile primite. Cea mai simplă modalitate de a rezolva problema este să pui un SET NOCOUNT ON la &amp;icirc;nceputul procedurii.&lt;/p&gt;&lt;p&gt;Problema e descrisă şi &amp;icirc;n următorul KB: &lt;a href="http://support.microsoft.com/kb/253240" title="http://support.microsoft.com/kb/253240" target="_blank"&gt;http://support.microsoft.com/kb/253240&lt;/a&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Răzvan&lt;/p&gt;</description></item><item><title>ado problems</title><link>http://sqlserver.ro/forums/thread/1293.aspx</link><pubDate>Mon, 11 Dec 2006 11:25:01 GMT</pubDate><guid isPermaLink="false">963f3a18-65dd-4aad-905c-b785cfe1d7c7:1293</guid><dc:creator>crestinul</dc:creator><slash:comments>0</slash:comments><comments>http://sqlserver.ro/forums/thread/1293.aspx</comments><wfw:commentRss>http://sqlserver.ro/forums/commentrss.aspx?SectionID=43&amp;PostID=1293</wfw:commentRss><description>&lt;p&gt;Am o aplicatie in care folosesc ado pentru apelarea unei stocate ce scrie randuri in niste tabele pe server.&lt;/p&gt;&lt;p&gt;Problema e ca atunci cand icerc sa scriu un rand care incalca o restrictie de unique a unui camp nu se ridica nimic la client nu apare exceptia totul pare ok ,desi pe server nu s-aapelat cu succes stocata,daca ruleze din sql queary analizer&amp;nbsp; obtin exceptia normal :Server: Msg 2627, Level 14, State 2, Procedure qualobiectivelacuri, Line 17&lt;br /&gt;Violation of UNIQUE KEY constraint &amp;#39;IX_StatiiCalitateLacuri&amp;#39;. Cannot insert duplicate key in object &amp;#39;StatiiCalitateLacuri&amp;#39;.&lt;br /&gt;The statement has been terminated.&lt;/p&gt;&lt;p&gt;Ce setare de ado trebuie sa fac ca sa apara exceptia pe client?&lt;/p&gt;&lt;p&gt;Multumesc&lt;/p&gt;</description></item></channel></rss>