Bug Alert WARNING: Do NOT Declare DAO Fields As Field2, Field3, etc. While declaring DAO Field objects as Field2 will get you additional IntelliSense, it comes at the risk of breaking working code when MS releases a new Field type.
Deployment Distributing One-Time Data "Hot Fixes" Rolling out changes to *production data* when you don't have direct access to that data can be tricky. This tip makes the process easier.
Defensive Programming In Defense of Security Through Obscurity There are two key elements to defending a military position: cover AND concealment. It's not an either-or proposition.
Defensive Programming A Safe Way to Add Temporary Code A quick tip to ensure your temporary code disappears when the sun sets.
Defensive Programming Frictionless Validity Checks Let's apply the concept of frictionless development to the defensive programming technique of data validity checks.
Defensive Programming Data Validity Checks Increase the quality of your existing data by running it through a series of validity checks and showing your users the results.
Defensive Programming 5 Ways to Reduce Logic Errors Using Automated Double-Checks Identify the critical functions in your application. Then, apply one or more of these techniques to ensure that if they break, someone will notice.
Defensive Programming Reduce Logic Errors in Critical Code Software Developers Can Almost Eliminate Logic Errors With This Powerful Technique
Defensive Programming The RecordsAffected Property is a Powerful Tool for Defensive Programming As developers, we need to constantly be thinking about how to handle unknown unknowns. The RecordsAffected property helps us do that.
Basic Avoid DoCmd.RunSQL in Microsoft Access If you are just starting out writing VBA in Microsoft Access, you may be tempted to use DoCmd.RunSQL. Don't. There is a better way.
Intermediate The "Unset" Enum Item This simple technique is a foolproof way to avoid the sort of logic bug that can live undetected in your codebase for years.