Designer/2000 FK constraints

In Designer one can set the optionality of a constaint as well as the optionality of the column. So, it is possible that a required constraint can have an optional column, or vice-versa, as a table definition. However, when you try to gen a module usung a column like that, it spits on you (as it should). Anyway, what I really want to know is how these two settings work with each other since I thought they both only contribute to whether the column is null or not null, right? Does one setting override the other or something? If they do only affect the optionality of the column, then if I would change a column and its constaint in the table definitions to be optional, the corresponding alter table statement would be to just make the column to allow nulls, right? Or, is it that Designer uses the Foreign Key optionality for generating the .fmb.

Thanks Received on Mon Mar 02 1998 - 00:00:00 CET