[AccessD] Access 2007 - The story so far.

If the VBA Code module were not enterable because of password protection,
right?  (getting a bit OT for Access... but I am curious, since Excel is my
favorite wild animal.)

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
Sent: Wednesday, August 17, 2011 3:54 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access 2007 - The story so far.

Interesting subject. I remember debugging an Excel VBA addin.
I discovered that if you didn't trap errors in a form's Initialize event,
Excel just "bugged-out".....completely...when an error occurred there.
No error message, nothing. This was back in the 2003 release.
>
> I'm in your camp (I think) on error handling.
>
> In development phase, I only use errorhandling when it is required for
> the logic (like back in the VB6 days, before collections had
> .Contains),
> or when there was a situation that I can't program around to prevent
> errors. (like if I am dividing by x, I can verify beforehand that x is
> not zero...but if I am sending a command to a database, and that
> command
> might fail, the only way to catch it is with errorhandling).
>
> Now most of my finished stuff has errorhandling through out, depending
> on the system, the platform and the processes.
>
> Drew


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com