[AccessD] VBAErrorHandler

No, that's just the thing...

It's not mentioned and if I don't set the project
properties Cond.Comp. to boolElE = 1, then
it skips right over and I don't get an error log
or debug.print.

I think?

Michael R. Mattys
www.mattysconsulting.com
----- Original Message -----
From: "John Colby" <jcolby at colbyconsulting.com>
To: <accessd at databaseadvisors.com>
Sent: Tuesday, June 03, 2003 10:21 AM
Subject: RE: [AccessD] VBAErrorHandler


> Michael,
>
> The stack stuff is code that tracks calls to functions.  If you turn on a
> property in the error handler setup then code to do te call trace will be
> inserted in the error handlers created.  In that case, the procedure stack
> code will be used.  I'm not sure what the conditional compilation variable
> is.  Is it mentioned in the doc anywhere?
>
> John W. Colby
> www.colbyconsulting.com
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Michael R
> Mattys
> Sent: Tuesday, June 03, 2003 10:13 AM
> To: AccessD
> Subject: [AccessD] VBAErrorHandler
>
>
> I am unclear on the following and could
> use some instruction:
>
>
> Public gProcStack As New adhProcedureStack
> is inside the class that is added to my project, but
> not defined outside the class when I set Conditional
> Compilation arg boolElE = 1. WriteErrorLog is also
> not defined.
>
> How am I to use these variables?
>
> Michael R. Mattys
> www.mattysconsulting.com
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>