View Single Post
  #14 (permalink)  
Old May 27th, 2010, 06:21 AM
ackid32 ackid32 is offline
Authorized User
Points: 208, Level: 4
Points: 208, Level: 4 Points: 208, Level: 4 Points: 208, Level: 4
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jan 2006
Location: , , .
Posts: 43
Thanks: 1
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by vb5prgrmr View Post
Well, to figure out where the error is coming from, and what line is causing the error, you should have proper error handling for your debug/beta testing. As an example...
Code:
Private Sub Form_Load()
 
On Error GoTo Form_LoadError
 
Exit Sub
Form_LoadError:
 
MsgBox "FormName.Form_Load " & Err.Number & ":" & Err.Description
 
End Sub
You can also add line numbers and use Erl (see MZTools for a nice addin for VB6.0 dev environment) to track down exactly which line is causing the problem. Also, put Option Explicit at the top of each code window, as this will force you to declare everything. Then if you have any On Error Resume or On Error Resume Next or On Error GoTo 0, remove them for proper error handling and in the future so you do not have to add this manually, goto tools>options and put a checkmark next to Require Variable Declarations. Then any new projects will automatically have Option Explicit at the top of each code window...



Good Luck
I already mentioned that the error was

"class does not support automation or does not support expected interface"
"Error No-430"
Reply With Quote