Posted by Jason Cumberland on 12/28/06 21:13

I would suggest adding a lookup value for "did not miss appointment"
and then storing the ID value of that in your appointments table. That
way you can keep the FK relationship and still have a valid value,
which you could even make the default value for the field for ease of
use.

On Dec 28, 1:57 pm, "Rico" <y...@me.com> wrote:
> Hello,
>
> I have a foreign key constraint between two tables (Appointments and
> MissedAppointmentReasons) and I'd like to allow null values in Appointments
> table for the field containing the MissedAppointmentReason, but currently, I
> get a Foreign Key Constraint Error when I try to add a record to the
> Appointments table.
>
> Any ideas how I can have the null values but still maintain the Foreign Key
> Constraint?
>
> Thanks!
> Rick

[Back to original message]