|
-
Feb 6th, 2000, 02:13 AM
#1
-
Feb 6th, 2000, 04:38 AM
#2
No, not really, but what I do is to put an ErrorRoutine in each of my procedures, and in that error routine I call a CommonErrorRoutine passing it the name of the calling procedure (unfortunately you have to hard-code the name). Since the Err object is global, CommonErrorRoutine can display messages or do whatever you want with Err.Number, Err.Description, etc.
------------------
Marty
What did the fish say when it hit the concrete wall?
> > > > > "Dam!"
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|