Specifically, the practice of manually checking ErrCode after steps that could catastrophically fail. It's a bit lazy, though for some types of code, the risk of an uncaught error is suitably low.
Wade.
Access: Runtime error 91.
- (acagle)
- (22)
- Dec. 27, 2004, 02:04:44 PM EST
I think that one means...
- (pwhysall)
- (10)
- Dec. 27, 2004, 02:17:51 PM EST
Re: I think that one means...
- (acagle)
- (9)
- Dec. 27, 2004, 02:25:41 PM EST
From the 10 Commandments of C Programming:
- (inthane-chan)
- (8)
- Dec. 27, 2004, 02:42:20 PM EST
So.
- (acagle)
- (7)
- Dec. 27, 2004, 04:08:09 PM EST
In VB?
- (JayMehaffey)
- (5)
- Dec. 27, 2004, 04:37:03 PM EST
Re: In VB?
- (acagle)
- (4)
- Dec. 27, 2004, 05:30:43 PM EST
You can use On Error GoTo
- (ben_tilly)
- (1)
- Dec. 27, 2004, 06:29:15 PM EST
That's still the way
- (Steven A S)
- Dec. 29, 2004, 03:37:21 PM EST
That was a joke
- (JayMehaffey)
- (1)
- Dec. 27, 2004, 07:33:54 PM EST
For certain techniques, it works.
- (static)
- Dec. 28, 2004, 05:30:48 AM EST
Opinions vary on "Global" error checking in VB.
- (mmoffitt)
- Dec. 30, 2004, 12:26:38 PM EST
That's the technical term "set"
- (FuManChu)
- (4)
- Dec. 27, 2004, 11:24:31 PM EST
Re: That's the technical term "set"
- (acagle)
- (3)
- Dec. 28, 2004, 05:28:42 PM EST
Yes, unfortunately.
- (FuManChu)
- Dec. 29, 2004, 02:26:17 AM EST
Putting it in every procedure is good practice for VB.
- (mmoffitt)
- (1)
- Dec. 29, 2004, 09:38:14 AM EST
Dangitall.
- (acagle)
- Dec. 29, 2004, 12:23:59 PM EST
Update: (+edit)
- (acagle)
- (5)
- Dec. 29, 2004, 12:57:53 PM EST
You're probably all over this, but...
- (Steven A S)
- (1)
- Dec. 29, 2004, 03:27:59 PM EST
Re: You're probably all over this, but...
- (acagle)
- Dec. 29, 2004, 03:47:06 PM EST
Where is the declaration exactly? And a few more q's.
- (mmoffitt)
- Dec. 30, 2004, 12:40:15 PM EST
Did you get this fixed?
-NT
- (mmoffitt)
- (1)
- Jan. 3, 2005, 08:33:37 PM EST
Re: Did you get this fixed?
- (acagle)
- Jan. 24, 2005, 05:36:50 PM EST