[AccessD] Lost Warnings...

There's the voice of experience talking!  ;-)

John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: accessd-admin at databaseadvisors.com
[mailto:accessd-admin at databaseadvisors.com]On Behalf Of Charlotte Foust
Sent: Wednesday, February 19, 2003 2:22 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Lost Warnings...


Don't put Echo = True in the exit block alone.  Put it in the error handler
as well, especially if anything is going to pop up a messagebox.  Otherwise,
you'll never see the messagebox and the routine won't fall through to the
Exit block.

Charlotte Foust

-----Original Message-----
From: Brett Barabash [mailto:BBarabash at tappeconstruction.com] 
Sent: 19. veljaca 2003 11:20
To: 'accessd at databaseadvisors.com'
Subject: RE: [AccessD] Lost Warnings...


One of the most valuable lessons that I learned the hard way is to ALWAYS
put the DoCmd.SetWarnings True, DoCmd.Echo True and DoCmd.Hourglass False in
the Exit block, if my routine alters those settings.  That way, if it
crashes, the error handler will cleanup after itself!

Ever have code blow up with Echo set to False?  Scariest damn thing I've
ever seen!


-----Original Message-----
From: Gustav Brock [mailto:gustav at cactus.dk]
Sent: Wednesday, February 19, 2003 3:35 AM
To: Drew Wutka
Subject: Re: [AccessD] Lost Warnings...


Hi Drew

> Interesting.  So if Access crashes, the docmd.setwarnings sticks in 
> the actual options, not just as a temporary flag eh?  I always knew to 
> be careful with SetWarnings, but I didn't realize it would stick from 
> session to session.