Hi,
I think the following is a bug in the OLEDB driver for SQL Server...

I can get ADO errors no problem, however when using SQLOLEDB, I get an empty
Err.Description from the
ADO.Error object. Below is a code snippet from MSDN

===============
'BeginDescriptionVB
Public Sub DescriptionX()

Dim Cnxn As ADODB.Connection
Dim Err As ADODB.Error
Dim strError As String

On Error GoTo ErrorHandler

' Intentionally trigger an error
Set Cnxn = New ADODB.Connection
Cnxn.Open "nothing"

Exit Sub

ErrorHandler:

' Enumerate Errors collection and display
' properties of each Error object
For Each Err In Cnxn.Errors

strError = "Error #" & Err.Number & vbCr & _
" " & Err.Description & vbCr & _
" (Source: " & Err.Source & ")" & vbCr & _
" (SQL State: " & Err.SQLState & ")" & vbCr & _
" (NativeError: " & Err.NativeError & ")" & vbCr
If Err.HelpFile = "" Then
strError = strError & " No Help file available"
Else
strError = strError & _
" (HelpFile: " & Err.HelpFile & ")" & vbCr & _
" (HelpContext: " & Err.HelpContext & ")" & _
vbCr & vbCr
End If

Debug.Print strError
Next

Resume Next

End Sub
'EndDescriptionVB
==================

When running this, I get the following in the Immediate Window:
Error #-2147467259
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
(Source: Microsoft OLE DB Provider for ODBC Drivers)
(SQL State: IM002)
(NativeError: 0)
No Help file available


However, thats were it stops. If I open a connection via SQLOLEDB and call
a store procedure that doesnt exist, all I get is a -2147217900 error. The
Err.Description is empty.

*** HOWEVER if I run the same code using MSDASQL.1 (OLE DB provider for SQL),
then I get the rich error information!!! ***

Error #-2147217900
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored procedure
'sp_NonExistant'.
(Source: Microsoft OLE DB Provider for ODBC Drivers)
(SQL State: 37000)
(NativeError: 2812)
No Help file available


Do you know anything about this bug? Do you know if Microsoft is planning
to release a SQL 2000 SP1, or a hotfix?
ps. I have found another bug with SQL 2000, is that if you install just the
Client Side tools, they have to go on C: !