This is the video I watched: Notes Anywhere!

What you are describing is basically a One to Many relationship.  Just like the Contacts in the Contacts and fleshed out in the Followups series.

You would NOT want multiple Notes tables i.e. Notes1T Notes2T.
You could call Contacts (NotesT) anything you want and have as many notes as you want for each customer.
To bring it into your form you just use the subform as described in the video.

On the other hand if you absolutely need 2 notes fields and are sure you will only ever need 2, you could make 2 notes fields in your NotesT table and give them different field names. Something along the lines of ProductNotes and AssemblyNotes, etc.

The better method would be to have a single notes field and also a category field where you could categorize the note.
Again see the videos above and also take a look at the Normalizing Data.

OK I just re-watched that video.
You could add a second note in like this.  I named mine SecondNote.
Change the Tag for that Note and also modify your code like so:

You will also need to change the after update event.

Private Sub Notes_AfterUpdate()

    CurrentDb.Execute "UPDATE NoteT SET NoteText=""" & Notes & """ WHERE NoteID=" & Notes.Tag
    Status "Note updated."

End Sub


Private Sub SecondNote_AfterUpdate()

    CurrentDb.Execute "UPDATE NoteT SET NoteText=""" & SecondNote & """ WHERE NoteID=" & SecondNote.Tag

End Sub


Thank you Scott Axton... I followed your suggestions and it worked perfectly!  I am assuming you are mentioning about the After Udate part because Richard puts up the message "Note Updated."  I am NOT using that comment so I believe I don't need to have an After Update event.  (I am the only user of the database and the notes in Note1 and Note2 are just for my information, and will not be updated.

Again, thank you very much!

Tom
If you want to edit it and have the changes saved then you need the AfterUpdate.
You don't need the Status.  See the difference between Notes and SecondNote above?