By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,567 Members | 1,670 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,567 IT Pros & Developers. It's quick & easy.

name of current procedure

P: n/a
Hi Folks

In Google, I read:

Jonathan Roenberg Mar 5 2001, 8:35 am
Is there a way in VBA to find the name of the current procedure at run
time?
This would be very helpful for some error checking I'm doing in my
code.
--
JR

Brendan Reynolds Mar 5 2001, 11:06 am
Unfortunately, no. You need to pass the name of the procedure as an
argument
to your error handling procedure. I usually pass both the name of the
module
and the name of the procedure. For the name of the module, I use a
module-level constant, as I will be using it in the error handler of
each
procedure in the module. You could use a constant for the procedure
name as
well, of course. I don't do that myself, though, as the call to the
error
handling procedure is usually the only place I'll use it.


Is this still the case or does Access 2003 has more options in this area?

Cheers
Nicolaas


Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On Sat, 28 May 2005 12:13:16 +1200, "windandwaves"
<wi*********@coldmail.com> wrote:

Same.
-Tom.

Hi Folks

In Google, I read:

Jonathan Roenberg Mar 5 2001, 8:35 am
Is there a way in VBA to find the name of the current procedure at run
time?
This would be very helpful for some error checking I'm doing in my
code.
--
JR

Brendan Reynolds Mar 5 2001, 11:06 am
Unfortunately, no. You need to pass the name of the procedure as an
argument
to your error handling procedure. I usually pass both the name of the
module
and the name of the procedure. For the name of the module, I use a
module-level constant, as I will be using it in the error handler of
each
procedure in the module. You could use a constant for the procedure
name as
well, of course. I don't do that myself, though, as the call to the
error
handling procedure is usually the only place I'll use it.


Is this still the case or does Access 2003 has more options in this area?

Cheers
Nicolaas


Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.