Different User IDs for Same Date, but Not Same User ID for Same Date

[Heatshiver]

I have two tables, a tblUsers and a tblDailyReport.

The tblUsers only stores a User ID. The tblDailyReport stores both the Date and the User ID. I have a relationship from tblUsers to the User ID on tblDailyReport. tblUsers has its primary key set to User ID. While tblDailyReport currently has no primary key.

When I use it this way I can have a User ID use more than one date. The issue here is that I can also have the User ID use the same date numerous times and have it stored in the tblDailyReport, creating multiple records for the same User ID and date.

If I make the Date in tblDailyReport a primary key, I can only use one User ID per date.



I need to ultimately have the same date but for different User IDs. However, I can't have duplicate records of the same date and User ID. What can I do to fix this?

[orange]

What exactly are you trying to do?
What is the purpose of each table?
What is the application?
What is the significance of UserId and Date?

[Heatshiver]

I am trying to be able to have different users fill out the same date as different records.

The tblUsers is so that the admins can input User IDs when they need to. The tblDailyReport is for the information that the user will fill out.

The application is for users to fill out daily reports.

UserID is significant because it ensures that only people given access can use the forms. The date is significant as it will be part of the search criteria for entering information on the forms and daily reports. They are in separate tables so that UserID isn't based on date, as it shouldn't be. However, the information filled out needs to not only have the UserID but the date the information was filled.

[orange]

Sorry, but your explanation hasn't helped me.
If you had to explain your situation to someone in a lineup at McDonald's, who knew nothing about Access or database, what would you say?

[Heatshiver]

Sorry, not always good at explanations.

What ended up fixing this is using a compound index primary key for User ID & Date on tblDailyReports. Now I can have different users make records for the same date, but a single user cannot make multiple entries for the same date.