[AccessD] event identification

Dan Waters dwaters at usinternet.com
Tue Nov 9 10:00:06 CST 2004


I asked this question once because I wanted to be able to record the
procedure name (automatically) when logging errors.  Mike Gunderloy
responded and said that the MS Access developers tried but were unable to
develop a reliable function to do that.

Rats!

Dan Waters
ProMation Systems

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Tuesday, November 09, 2004 9:39 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] event identification

Is there any way to determine "what" event is triggered when without adding
a lot of very specific Debug.Print statements to each possible event
procedure? 
 
I'm wondering if there isn't some generic property that will define the
calling event procedure? Is there such a critter? 
 
For instance, if a command button's Click event is triggered, is there some
generic way I can print "Click" to the Immediate window? I know I can do
this easily enough by adding a Debug.Print "click" statement myself, but is
there a GENERIC statement that I could add to any event that would define
the calling event? 
 
I hope I'm making myself clear. 
 
Susan H. 
-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list