by MYLE
17. March 2011 06:54
- Make sure you start with a properly-normalized database design and that you understand all of the fields and relationships before beginning to code.
- Don't allow users to see or edit tables directly, but only through forms. Don't use "Lookup Fields" (at least, not on a table level) either, as they can lead to confusion.
- Choose a naming convention and use it. Never allow spaces in names.
- Write comments in your procedures and explain each variable. Do this as you code: don't rely on going back "once the program's done".
- Understand error handling and use it faithfully in all procedures.
- Split your databases into a front-end and back-end.
- Don't use Autonumber if the field is meant to have meaning for the users.
- Don't copy and paste other people's code without at least attempting to understand what it does.
- Don't use "SendKeys", "Smart Codes" or "GoTo" (unless the GoTo is part of an OnError process)
- Back-up the database faithfully. Never make changes on the Production Database, but on the Prototype Copy instead.
d2ebde4c-29a6-4cbb-a53f-a96ffccb3ad4|0|.0