Setting up Customer ID as Primary Key

That worked perfectly. I will have to do some more research on that code to get a better understanding of it though. 

Would it be a similar procedure for the Color subform? If I wanted to allow the user to create a new entry into the Color subform to add a color that wasn't there? If I were to add some event procedure or code into the fsubCustColorPreference form, would it be applied or inherited if I were to use it as a subform in frmCustomers?

For a combo box to both navigate to a customer record, and go to a new record (thus avoiding the need for a separate button) you'd replicate that in my demo by having the following as the combo box's RowSource:

SELECT CustomerID,

FirstName & " " & LastName, 1 As SortColumn,

LastName,Firstname  

FROM Customers  

UNION

SELECT 0, "<New Customer>", 0,"",""  

FROM Customers

ORDER BY SortColumn, LastName, FirstName;

It's other properties would be:

BoundColumn:   1

ColumnCount:    2

ColumnWidths:  0cm

If your units of measurement are imperial rather than metric Access will automatically convert the unit of the last one to inches.  The important thing is that the dimension is zero to hide the first column.

The code for the combo box's AfterUpdate event procedure would be like this:

    Const MESSAGETEXT = "No matching record"

    Dim ctrl As Control

    Set ctrl = Me.ActiveControl

    If Not IsNull(ctrl) Then

        If ctrl = 0 Then

            ' go to new record and move focus to FirstName control

            DoCmd.GoToRecord acForm, Me.Name, acNewRec

            Me.FirstName.SetFocus

        Else

            With Me.RecordsetClone

                .FindFirst "CustomerID = " & ctrl

                If Not .NoMatch Then

                    ' go to record by synchronizing bookmarks

                    Me.Bookmark = .Bookmark

                Else

                    MsgBox MESSAGETEXT, vbInformation, "Warning"

                End If

            End With

        End If

    End If

The code for the form's Current event procedure would be:

    ' synchronize go to contact combo box

    ' with current record

     Me.cboGotoCustomer = Me.CustomerID

where cboGotoCustomer is the name of the combo box.

The code for both the form's AfterUpdate event and AfterDelConfirm event procedures would be:

     ' requery go to contact combo box

     ' to reflect changes to data

     Me.cboGotoCustomer.Requery

    ' synchronize go to contact combo box

    ' with current record

     Me.cboGotoCustomer  = Me.CustomerID

With a bound form you don't need a button to save the record.  This is automatically done when you move to another record, close the form or explicitly save the record in some other way such as clicking on the record selector.

I am having trouble controlling the Record it's at with the combo box with using the tabs. I want to be able to navigate the records, as you have in your demo, and I want to be able to add new records too. I added a "Add Customer" button to add a new record and a "Save Customer" to save the information and refresh the page. I don't want them to be able to add new records with the combo box, just go to that record. I tried using a macro for "Go To Record", but it was not working.

It is under the form: frmCustomers

http://infernalrage.com/i/InfernalRage_2.accdb

Is there a recommendation on using more than 1 form to enter data into 1 table?

It's entirely a matter of your own choice.  Both will do the job.  If you use two forms, however, once you've entered all the data you have to open both to see it all.  A better solution would be to use a single form and put a tab control in it.  You can put controls bound to the primary fields on the first page of the tab control, controls bound to the secondary fields on the second page, and the colour preferences subform on the third page.

In the form's header section you can include an unbound combo box to enable you to move to a selected customer record.  You'll find an example of a combo box used in this way in FindRecord.zip in my public databases folder at:

https://onedrive.live.com/?cid=44CC60D7FEA42912&id=44CC60D7FEA42912!169

If you have difficulty opening the link copy its text (NB, not the link location) and paste it into your browser's address bar.

In the same OneDrive folder is also a FormsDemo file which includes an illustration of how to place subforms on pages of a tab control.

Is there a recommendation on using more than 1 form to enter data into 1 table?

I combined the Customer and CustomerProfile table into just a single Customer table so the customer demographics and the preferences are in one table. Currently, all the information is received at once, but in the future I may receive the customer demographic at one time and then the Customer Profile information at another time. Would it be better to split the tables up or use more than 1 form to enter the data?