Jim,

If you choose all fields in your SELECT statement, like " Select Parent.*, Child.*..... " with a left join to the child table then your result cursor will have .Null fields for the PK and FK fields from the Child table where there are no matches. I imagine that's what Dennis is referring to, not .Null values in the original tables' PK values.


>Besides, why is it possible that a PK field can be NULL? A foreign Key may be NULL representing no reference and in that case I would probably want the NULL so I can tell the difference between a key of 0 and no key value at all.