That's the technical term "set"

Post #188,360 by FuManChu 12/27/04 11:24:31 PM Reply	That's the technical term "set" Most likely, you have a bare assignment like Object = New Thing ...that should be using the Set command instead: Set Object = New Thing
Post #188,421 by acagle 12/28/04 5:28:42 PM Reply	Re: That's the technical term "set" I am, in fact, using Set: Set cls_BatchALSAdd = New clsBatch I am believing more that I need to trap all my own errors to avoid having Access void the objects when it generates an error. I do not want to do this by putting an On Error Goto Errhandler in each and every procedure though. Can't figure out where to put it though. I can't put it outside of a procedure, but otherwise I (think I) have to put it in every procedure.
Post #188,452 by FuManChu 12/29/04 2:26:17 AM Reply	Yes, unfortunately. Which is why trapping sucks as a debug technique in VB/VBA. Liberal use of debugger breakpoints will point out the offending code quicker. Which still isn't fun. :(
Post #188,468 by mmoffitt 12/29/04 9:38:14 AM Reply	Putting it in every procedure is good practice for VB. Even if it's just to write to an error log and continue. I've been coding VB for more years than I care to admit (Versions 3-6, am doing a lot less now), but I always made every "Sub" routine a Function that I could and returned a boolean. Each Sub and Function had its own error trap. Sucks, but there you are. bcnu, Mikem Eine Leute. Eine Welt. Ein F\ufffdhrer. (Just trying to be accepted in the New America)
Post #188,479 by acagle 12/29/04 12:23:59 PM Reply	Dangitall. Oh well, I guess I shall start putting them in. . . .sigh

Welcome to IWETHEY!