If Phone Number is the primary key, they will not be able to change it to a
duplicate value: primary keys have unique indexes on them. I take it you
want to intercept before you get to the point of trying to make the change
in the database.
In the Phone Number text box's AfterUpdate event, do a query of the database
to see whether that value already exists. You can use the DLookup or DCount
function if you like, or you can open a recordset.
However, is Phone Number really a good choice for a primary key? Are you
positive you'll never have two customers with the same phone number?

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
> To help you understand my problem and assist me, I will give an actual
> illustration. I have a table that consists of CustomerPhone, Name, Address
[quoted text clipped - 20 lines]
>
> PS. The key thing to remember is the form consists of unbound controls.