Referential Integrity does not prevent Nulls in the foreign key field.
Open your related table in design view.
Select the foreign key field.
Make sure it has no Default Value set, and its Required property is No.
Of course, the primary key cannot be null.

Signature
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
>I have a number of worksheets that have their own id's and these are
> connected to a project summary table. Which will not accept nulls due
> to the Ref Int. As the summary table is more likely to have nulls than
> anything else, can I change settings to allow null values. Or do I
> have to delete the summary table.
will - 16 Aug 2006 20:55 GMT
another note to make. Don't forget if you are making changes to a field that
is used in relationships, alot of times you have to delete that relationship
before you can save the changes to that field.
> Referential Integrity does not prevent Nulls in the foreign key field.
>
[quoted text clipped - 9 lines]
> > anything else, can I change settings to allow null values. Or do I
> > have to delete the summary table.