Developer Forum

Hi,

We have a VB6 application that is being used for years without a single
problem.
The application connects to SQL Server 2000 (last service pack) through
the OLEDB driver.

Problems started when we upgrade to win XP pro SP1

at this line
conn.execute "myStoredProcedure (1,2)"

conn is an ADODB.Connection object.

the application stops in WIN XP with the following very helpful :-) error
"unspecified error"

at the SQL side the stored procedure runs sucessfuly (this can be seen
in MS profiler), the problems seems to be at ADO/VB side

any ideas??

Thank you.

Hi,

Did you try to declare parameters explicitly, not pass then inside of the
string? Also try to remove parentheses

conn.execute "myStoredProcedure 1, 2"

--
Val Mazur
Microsoft MVP
Check Virus Alert, stay updated
http://www.yqcomputer.com/


"msnews.microsoft.com" < XXXX@XXXXX.COM > wrote in

Thank you.
i found the reason, and is a very strange one :-)

well, the problem was a syntax error in one of our scripts.

The curious behavior is when ADO reports the error only in win xp pro
sp1 clients and ignores it in all the others OS (madac/ado versions).

Cipriano.