DB_E_ERRORSINCOMMAND ( HRESULT = -2147217900 )

Hai all,
I am getting an DB_E_ERRORSINCOMMAND exception when I try to open a
recordset or execute query in VC++. But when I run the same query in
Query Analyzer, it is working fine. I am sure the connection string is
correct. I am running a collection of queries and finally commit the
transaction, but everytime it not throwing the exception on same query,
eachtime different queries throw exception randomly.
Can anyone tell whats the problem?
Urgent, Please help...
Looking forward for the response..
Thanx in advance...
Hi
Have you printed out the SQL Statement before you send it to the server? You
may want to use SQL Profiler to see what/if anything is being sent to the
server.
Have you also checked out
http://support.microsoft.com/default...b;en-us;18189?
John
"Prince" wrote:

> Hai all,
> I am getting an DB_E_ERRORSINCOMMAND exception when I try to open a
> recordset or execute query in VC++. But when I run the same query in
> Query Analyzer, it is working fine. I am sure the connection string is
> correct. I am running a collection of queries and finally commit the
> transaction, but everytime it not throwing the exception on same query,
> eachtime different queries throw exception randomly.
> Can anyone tell whats the problem?
> Urgent, Please help...
> Looking forward for the response..
> Thanx in advance...
>
|||Hai,
Thanx for ur reply...
In ran the query from Profiler, it works fine... and the URL that u
provide doesnt works...
Looking forward for the response...
John Bell wrote:
[vbcol=seagreen]
> Hi
> Have you printed out the SQL Statement before you send it to the server? You
> may want to use SQL Profiler to see what/if anything is being sent to the
> server.
> Have you also checked out
> http://support.microsoft.com/default...b;en-us;18189?
> John
> "Prince" wrote:
|||Hi
Try http://support.microsoft.com/kb/181890
You may want to check MDAC versions.
John
"Prince" wrote:

> Hai,
> Thanx for ur reply...
> In ran the query from Profiler, it works fine... and the URL that u
> provide doesnt works...
> Looking forward for the response...
>
> John Bell wrote:
>
>