Can I have a bit of guidance on how to create a database layout to ensure I don't allow repeated data. The part of the layou that concerns me is needing to use two fields.

So I define a meeting as date and location, but there could be multiple meetings so date and location aren't unique but together they are. Like wise an event is the combination of a meeting and an event number.

Is using this structure okay?

Meeting - Using Numerical ID key
Location - text
Date - datetype.

Event - Numerical ID
Event Number
Meeting ID


Is it okay to use a structure like this with numerical ID's it wont allow uniqie combinations of date & location or MeetingID & event to be entered will it?