ID........field1..........field2....field3....field4....field5....field6
12345...VISA............x..........x..........x.........x..........x
12345...AuthType7.....x....................x..........x..........x
12345...AuthType2................x.........x.......................
12345...AuthType8................x.........x......................x
55446...AuthType7.....x....................x...........x..........x
55446...AuthType2................x.........x.......................
77668...VISA............x..........x..........x.........x..........x
77668...AuthType3...................................................
77668...AuthType9...................................................
99889...VISA............x..........x..........x.........x..........x
99889...AuthType9...................................................
99889...AuthType7.....x....................x...........x..........x

4 Tables:
Auth - records of authorizations, as shown above
AuthType - a one-field table, list of "AuthTypes", linked to "field1" of this Auth table by combobox
Person - ID (primary key), name, login initials, etc
Org - list of organazines, supervisor, etc, for Person table information

What I need to do is to have somehow "required" fields filled in. I want to have this in "Field Validation" in the Table design, but I don't know how to do such like this above. Like field5, some must have data filled in (VISA and AuthType7), while some other don't.

I thought about having the AuthType table having the same fields as the Auth, and put logical for field type (T/F), so that the code can do a field checking by looking at the AuthType table? I want to be able to have this possible for while even in the BROWSE edit mode too. This list would be in the child grid too. If it must be in a class code or DLL or whatever, thats fine. This seems to be the toughest one for me (and I ensure you, tough for you too :)

What you suggest or if you don't understand, ask me please. We even hired someone outside to do this, and this person screw up by having to do something else (fixing some other client's server). We are still waiting, but I feel he won't make it.

Chuck