Hi Christian,

>> You define the PKs as a non-nullable datatype - like you already do.
>> You define the FKs as the same datatype, but nullable. For instance:

> Even when I define the FKs as nullable, I get an error that the FK
> may not be NULL.

That's strange. Which server do you use? Are you sure the error comes
from the server and not from some frontend that does its own thinking?

I use this nullable-FK approach sometimes (and other times the
approach Helen described) and it works; I can happily insert records
with nulls in the FK field. I even tested it before I posted my
reply, just to be absolutely sure.

But anyway, your problem is solved; that's the most important thing.


Greetings,
Paul Vinkenoog