Suggestions for coding:

1. Make sure *every* module has:
   Option Explicit
at the top. Access will automatically add this to all new modules if you
check the box under:
   Tools | Options | Editor | Require Variable Declaration
(from the code window.)

2. Whenever you are referring to an object on the form you are coding in,
use Me rather than Forms!Form1. VBA knows the names of the objects on this
form.

3. For controls in a form/report, use the dot (.) rather than the bang (!),
e.g.:
   Me.Text0
VBA will autocomplete the name for your (press Tab to accept the name). This
really cuts down the misspelt names, as well as being faster to type. You
still need the bang for fields of a recordset. (I personally use the bang
for fields from the form's recordset that are not represented by controls on
the form, as Access can be inconsistent about recognising these.)

4. Use tab indents for block operations (such as If ... End If). I actually
type the End If immediately after the If line, and then jump back up to
enter the other lines between them. This cuts down on the chance of
mismatched blocks.

5. Always Compile (Debug menu) before running your code.

6. If you use error handlers, disable them until the code is tested, so you
can see what line is failing. More info on error handlers:
   http://allenbrowne.com/ser-23a.html

Heaps of other wider suggestions as well, such as typing as narrowly as
possible, scoping as narrowly as possible, thinking event-driven, writing
modular (small) reusable procedures, breaking out a process that is likely
to error into another function, using the return value of functions to
indicate success/failure if nothing else is obvious, naming conventions,
always handling Null, remembering the "other" possibility (e.g. Case Else),
cleaning up, testing and debugging at each stage, handling
extreme/unexpected values, etc, etc.