Drew Wutka
DWUTKA at Marlow.com
Wed Aug 17 13:52:13 CDT 2011
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 -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William Benson (VBACreations.Com) Sent: Tuesday, August 16, 2011 9:41 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Access 2007 - The story so far. WTF = "Why'd That Fail?" ... we all know our acronyms. Could this be vindication of my strategy of using no error handling? (Apologies to Emilia and others who have tried to reform me for such a paltry joke). -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins Sent: Tuesday, August 16, 2011 10:28 PM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Access 2007 - The story so far. Well I have been trying to find something nice to say about A2007, and I guess one thing is in form design view when you have all the controls grouped and you expand or contract one of them, the rest move along in sync, that is nice and can save a fair bit of time tweaking the form layout etc. Sadly, it doesn't make up for the rest of the bugs and nonsense I have come across, but hey, it is something at least :) Latest weirdness was I had a file whose ADO connection string to the back-end was failing. No idea why as it was working great on other PC's, so I took the error handlers off the all the code so I could see exactly which line was failing. Ran the code and it worked perfectly, WTF?? I mean, I didn't put in an "On error resume next" I took out ALL the error handling functions so it would go splat at the first problem, but instead it work flawlessly first time. So I put back in the error handlers to see what might happen - maybe they were causing the error somehow (although it was compiling just fine), and it worked flawlessly again. Go figure. I fixed the problem, but no idea what happened or why that would fix the issue.... Many instances of this sort of weirdness. If you are just mashing data A2007 works mostly ok, but to develop an app in A2003 is far more stable and easy to use. Approach with some caution if you can. Just me thoughts Cheers Darryl. -- 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 The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI Business Sensitive material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.