this is from msdn...
You create custom errors by using the VB built-in vbObjectError constant, then adding an offset. Microsoft reserves error values between vbObjectError and vbObjectError + 512, so you must start custom errors at offset 513 or greater. The vbObjectError constant is equivalent to hex value 80040000, which prints out as value -2147221504 if you display its decimal equivalent. Therefore, it's often convenient to display custom errors as hex values (using the Hex$ function), as shown in the ClassErr routine.
im think i may be more confused. i belive a type mismatch is '13'. how is this so if the base is way into the negatives?
basically, i just one error number that i can use that will not be used by ado, cdo ... or any of the other libraries i am using.
thanks - u
Main Topics
Browse All Topics





by: TimCotteePosted on 2001-10-05 at 08:25:24ID: 6530991
By VB as such yes, however various components that you use in VB such as ADO may well generate error numbers less than one. Equally an error that is caused by VB but is actually reported by the operating system may also be less than one. There is a reasonably complete list of errors on MSDN, do a search on LONG TRAPPABLE either on your own copy or on the net at msdn.microsoft.com