Creating Relationships: Is this a reasonable Relationship?

[RootMason]

Thank you, that was very helpful

[RootMason]

I've managed what I think will be a reasonable database, but I am stuck on creating Lookups for my Timesheet (tblTimesheet) and Expenses (tblExpenses). For example, on the form I'm trying to create, it relies partially on tblProjects, which has 3 necessary columns, ClientName, TaskTitle & ProjectCode. The dropdown list on the form only needs the first two for an employee to be able to identify the project & task, but the Timesheet table needs to have the ProjectCode and NOT the ClientName or TaskTitle.

Any suggestions on how to create a Lookup that can accomplish that?

Thanks again for all your time!

Steve Clark

[RootMason]

Would this be better presented as a new question on the forum, do you think? I get emails for every post I respond to on LinuxQuestions forum and it can get a bit frustrating... again, thanks for all your help. The naming conventions were very helpful. I'll dig into the UMLs later as well.

[ItsMe]

What do you mean by lookup? Are you referring to lookup fields? I would advise against lookup fields. Don't get too excited about UML. If you plan on making a career out of developing apps and collaborating with others then, study UML. I mention it only to convey the message that models can exist on paper and outside of Access.

[RootMason]

I'm now trying to make some mock-up forms for employees to be able to log on and use the form to enter data into the database. I'm using lookups to create dropdown menus to select the client they worked for for the hours they enter. Am I using the terminology wrong? Or perhaps there is a better way of doing this?

I'm not going to jump into UML too hard (at least not right now), but I can see how it will map out more specifically what's going to happen. It didn't seem to be too necessary to the task at hand. The drawing I did on paper literally looked just like the snapshot of the relationship window I first posted, being the only way I pictured being able to draw it out.

I'm also stuck on the idea that, after the employee logs on (enters their password), the form I'm trying to create uses that employee for the timesheet entry, and not that they have to pick themselves from another dropdown menu of employees.

On a personal note, hope you had a good Christmas and have a happy new year! Thanks again for your direction!

Steve Clark

[ItsMe]

Info on lookup fields
https://www.accessforums.net/databas...tml#post202717

Overview of using and building comboboxes
http://datapigtechnologies.com/flash...combobox3.html

An example of basing a form or subform recordsource on a combobox
https://www.accessforums.net/forms/f...ing-40395.html

I have not looked at this example but there are a few examples of creating user logins and keeping track of users.
https://www.accessforums.net/forms/c...tml#post205098

Some discussions on user logon forms
The approach I describe in this link does not fully explain why I choose to use a public variable for the UserID
https://www.accessforums.net/forms/r...orm-38856.html