[AccessD] C2DbShutdown

You never really said what specifically the problem was, how it expressed
itself, nor how it could be avoided.

>because if the VBE editor has been opened, the callback capability goes
bezerk, and sends the VBE into an endless loop, which makes Access look like
it has locked up.

What does that mean?  Just opening ANY MODULE in the application causes
Access to lock up?  Opening the module with that functionality in it causes
ACCESS to go beserk?  Stepping into the function with that code?  Stepping
over that line of code?

If opening ANY MODULE causes that then I for one would never use that
method.  If either of the other three, then I could place it in it's own
module and deal with the problem.

John W. Colby
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of
DWUTKA at marlow.com
Sent: Wednesday, February 25, 2004 5:40 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] C2DbShutdown


LOL.  Figured that.  It's really only a development warning, because you
should never allow your users to get into your source code anyways, so as an
.mde, or a fully developed function, the warning doesn't apply.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John W. Colby
Sent: Wednesday, February 25, 2004 3:48 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] C2DbShutdown


The WARNINGWARNINGWARNING mostly.  ;-)

I haven't decided not to use that method but I likewise haven't decided to
use it.

John W. Colby
www.ColbyConsulting.com