H
Harperec
Hi All,
I've got a database with the structure given below. in the Booking
Table, I want to make sure that I don't get entries that have the same
date and TableID as another record. I was thinking that a
multiple-field primary key would be the way to acomplish this, but
reading up on those, they will create headaches in the long run. How
can I ensure that I won't double book a table on a particular date?
Thanks!
-eharper
tblTable
pkTableID
Venue
TableType
MaxPartySize
tblAvailableDates
pkDates
tblCustomers
pkCustomerID
LastName
FirstName
ContactInfo
tblVenue
pkVenueID
tblBookings
pkBookingID
Date <---
TableID <---
CustomerID
I've got a database with the structure given below. in the Booking
Table, I want to make sure that I don't get entries that have the same
date and TableID as another record. I was thinking that a
multiple-field primary key would be the way to acomplish this, but
reading up on those, they will create headaches in the long run. How
can I ensure that I won't double book a table on a particular date?
Thanks!
-eharper
tblTable
pkTableID
Venue
TableType
MaxPartySize
tblAvailableDates
pkDates
tblCustomers
pkCustomerID
LastName
FirstName
ContactInfo
tblVenue
pkVenueID
tblBookings
pkBookingID
Date <---
TableID <---
CustomerID