5) Go back to the calling buttons and change the form calls to
include
(using your field names) the criteria of
         "[ID] = " & me.ID

In the ONClick event of the button to call the other form you will
find something like this

Private Sub Command21_Click()
On Error GoTo Err_Command21_Click

   Dim stDocName As String
   Dim stLinkCriteria As String

   stDocName = "Form2"

   DoCmd.OpenForm stDocName, , , stLinkCriteria

Exit_Command21_Click:
   Exit Sub

Err_Command21_Click:
   MsgBox err.Description
   Resume Exit_Command21_Click

End Sub
====================

What you want to do is to add the criteria..
so it will become something like this.

Private Sub Command21_Click()
On Error GoTo Err_Command21_Click

   Dim stDocName As String
   Dim stLinkCriteria As String

   stDocName = "Form2"

   stLinkCriteria = "[ID]=" & Me.ID
   DoCmd.OpenForm stDocName, , , stLinkCriteria

Exit_Command21_Click:
   Exit Sub

Err_Command21_Click:
   MsgBox err.Description
   Resume Exit_Command21_Click

End Sub
============================

Without that extra little bit of criteria, you were simply looking at
ALL of the records in the subform.
With the criteria you will only get the records that belong to the
main form.

You almost had it.    But you will NEVER forget it once you see it
working.......

Ron

Ron, this worked great buy I have another question.  To make these forms as
idiot proof as possible I need to add something.  During testing, I entered
test data through my forms and noticed out of habit I often hit the enter key
instead of the tab key to move from one field to the next.  I typed the date
in the first fied, hit enter, and it created a new record instead of going to
the next field in the form.  Do you have code that will cause the form to
treat the enter key as if it were the tab key and send the cursor to the
following field, or even to disble the enter key all together.  The users for
this database range from novice to less than novice.