dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: Enterprise
Expertise: Beginner
Aug 21, 1997

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


ODBC Error Display

I have seen many posters in the VB newsgroups that say they have received an ODBC error message such as 3146, but can't figure out why they got the message. I suspect that the vast majority of these posters did not update their error-handling procedures to use the DBEngine.Errors collection when VB4 was released. Using this collection usually gives them all the error messages they need to resolve the problem. I have created an error-handling subroutine that displays the correct error message based on whether the error is a DB error:
 
Public Sub ShowError()
Dim sError As String
Dim nI As Integer
Dim sTitle As String
	sError = ""
	' Determine whether or not this is a 
	' database error
	If DBEngine.Errors.Count > 0 Then
		If DBEngine.Errors(DBEngine.Errors.Count - 1)._
			Number = Err.Number Then
			sTitle = "Database Error"
			For nI = 0 To DBEngine.Errors.Count - 1
				sError = sError & DBEngine.Errors(nI) & _
					vbCrLf
			Next
			sError = sError & vbCrLf
		End If
	End If
	If sError = "" Then
		sTitle = "Error"
		' add the error string
		sError = sError & Err.description & vbCrLf
	End If
	' beep and show the error
	Beep
	MsgBox sError, , sTitle
End Sub
Karl Costenbader
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date