Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MS SQL 2000 & ADO Connection.Errors Problem

Status
Not open for further replies.

Toyman

Programmer
Jun 19, 2001
68
GB
Hi
I have the following problem.
I'am using the ADO (2.5) object to call stored procedures in MS SQL 2000. In the SPs I do error checking and do a raiserror. With a Win98 Client the error description in Connection.Errors(x).Description is returned, but not with a Windows2000 Professional Client. I even compiled the VB application under Win2k Pro but it still doesn't work.

At the end I greated my own message with sp_addmessage and only returned the native number. This works but if I want to have an native number with several error descriptions, this can not be done because of the above problem....

Anyone have the same problem and know how to fix it.

Thanks
Toyman
 
Do the Win98 and Win2k machines have the same versions of MDAC installed? If not, that may be the reason for the difference.

There is a known bug in Windows 2000 RTM (COM+) that may also be the cause. Install Windows 2000 SP1 to fix it.

Another possibility is outlined in this article about SQL 7. May not be applicable in your case.

PRB: ADO Errors Collection Does Not Contain User-Defined Error Messages
Terry L. Broadbent
faq183-874 contains some tips and ideas for posting questions in these forums. Please review it and comment if you have time.
NOTE: Reference to the FAQ is part of my signature and is not directed at any individual.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top