C
ChrisBarnes
I am currently designing a database to record group trips within our
organisation.
I have normalised the data down as far as I can and now want to start
thinking about the general flow of information and rules for it.
I want to make sure that only eligable groups can have a record added to my
trips table, I have set up a relationship from the groups table (which has a
logical field called Eligable) to the Tbl_Leaders table, which in turn is
linked to the trips table via LeaderID (Primary key 1 to Many relationship)
How can I set up validation rules/VB to make sure that only group types
which have the eligable flag marked as true can have a record added to the
trips table?
Also, is there any way that I can have the TripID field inserted
automatically as I drill down through the tables or should I rip it up and go
un normalised?
TIA
C
organisation.
I have normalised the data down as far as I can and now want to start
thinking about the general flow of information and rules for it.
I want to make sure that only eligable groups can have a record added to my
trips table, I have set up a relationship from the groups table (which has a
logical field called Eligable) to the Tbl_Leaders table, which in turn is
linked to the trips table via LeaderID (Primary key 1 to Many relationship)
How can I set up validation rules/VB to make sure that only group types
which have the eligable flag marked as true can have a record added to the
trips table?
Also, is there any way that I can have the TripID field inserted
automatically as I drill down through the tables or should I rip it up and go
un normalised?
TIA
C