Steve,

Ummm, do you get a message? What happens when you try?

I'm going to make a suggestion here... I would have set up the table
differently...

tblPeople
pPeopleID (PK - Autonumber)
pBadgeID (Set to no duplicates but I can change when I like)

tblEvents
eEventID (PK)
eDirector (FK-linked to pPeopleID)
eManager (FK-linked to pPeopleID)

The above way allows you to set Referential Integrity without worrying about
Cascading Updates. A Primary Key should be used to relate records and you
should not care what it is. Okay, enough with my two cents worth!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"Steve Haack" wrote in message
...
I have a field called tblPeople. It has an AutoNumber field as its PK, it
has
a field called ID which is a text field, indexed (no dupes).

I have another table called tblEvents. In tblEvents I have amongst others,
two fields, Manager and Director. I am trying to create relationships
between
tblEvents.Manager and tblPeople.ID, and also between tblEvents.Director
and
tblPeople.ID. I have done that.

What I can't do though, is set Referential Integrity with Cascading
Updates
so that if a person's ID changes (which it can, since it is an ID Badge
Number) it updates the records in tblEvents.

Any ideas?