Hi all,
I'd just like some suggestions on how to go about designing the tables for this database.
It is somewhat of a schedule system.
I have multiple users.
A user will enter a date and a form will display that date and the next 6 days (ex: if user enters 1/1/2004..it will show that and 1/2/2004, 1/3/2004 etc.
Now on every date they will select a time and then enter info such as: location, city,company, etc.
This info is unique to the time and date.
Here's what I have been thinking:
1) Userinfo table: (UserID, UserName)
2) Schedule table: ScheduleID, Time, Location, city, company
3) User Schedule table: ScheduleID, UserID, Date.
I've done a test run on this but hasn't worked out so great.
Is simply using 2 tables enough here? (UserInfo and Schedule table including date)
Any suggestions would be greatly appreciated. Thanks!
I'd just like some suggestions on how to go about designing the tables for this database.
It is somewhat of a schedule system.
I have multiple users.
A user will enter a date and a form will display that date and the next 6 days (ex: if user enters 1/1/2004..it will show that and 1/2/2004, 1/3/2004 etc.
Now on every date they will select a time and then enter info such as: location, city,company, etc.
This info is unique to the time and date.
Here's what I have been thinking:
1) Userinfo table: (UserID, UserName)
2) Schedule table: ScheduleID, Time, Location, city, company
3) User Schedule table: ScheduleID, UserID, Date.
I've done a test run on this but hasn't worked out so great.
Is simply using 2 tables enough here? (UserInfo and Schedule table including date)
Any suggestions would be greatly appreciated. Thanks!