X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
   Reply to this topicStart new topic
> Show Next Task Deadline In Projects Datasheet, Access 2016    
post Feb 11 2019, 01:24 PM

Posts: 7
Joined: 7-February 19

I have been fighting with this one for a couple of days, and I just can't figure exactly how to accomplish it.

I have a Projects Table (Image 1) and a Tasks Table (Image 2). Under each project there are tasks that are associated with them and for each task there is a start date and a deadline date.

What I would like to show on the Project List (Image 3)page what is the next task deadline date that is upcoming. I was able to do a Select statement but it is showing all of the task dates for every project in a combo list. I also did a different statement that is showing only the first record of the task table but it is the same for each project.

So I decided to do a Query(Image 4) which is showing the each task Due_Date with the corresponding Project Name ...

Ultimately I would like to be able to show the Due_Date and use conditional formatting with color to alert the user that a milestone due_date is within 5 days of today ...

Any thoughts or ideas on how I would be able to accomplish this?

Images of the table attached ... Thank you all !
This post has been edited by 3dzer0: Feb 11 2019, 01:26 PM
Attached File(s)
Attached File  Image_1.JPG ( 31.68K )Number of downloads: 2
Attached File  Image_2.JPG ( 83.22K )Number of downloads: 3
Attached File  Image_3.JPG ( 46.6K )Number of downloads: 1
Attached File  Image_4.JPG ( 36.33K )Number of downloads: 2
Go to the top of the page
post Feb 11 2019, 01:30 PM

UtterAccess VIP
Posts: 13,034
Joined: 6-June 05
From: Dunbar,Scotland


I am a little concerned about your table structure(s).

Your Projects table should have ProjectID as the Primary Key - Autonumber.

Your related Tasks table should have TaskID as the Primary Key - Autonumber and the related Foreign Key you need ProjectID - Number.

You would then link ProjectID to ProjectID and set Referential Integrity.

Hope this helps?


Get happiness out of your work or you may never know what happiness is.

Go to the top of the page
post Feb 11 2019, 01:34 PM

Posts: 7
Joined: 7-February 19

Under the Projects Table and the Tasks Table each has an ID that are Primary Keys .... and Auto numbered. I'm not sure what Referential Integrity is though...
Go to the top of the page
post Feb 11 2019, 01:43 PM

Posts: 7
Joined: 7-February 19

I'm sorry I do understand what you are talking about.. you mean the relationships.

Here is what I have in the image below.

I think it is set up correctly ... Maybe ..
Attached File(s)
Attached File  Image_5.JPG ( 81.28K )Number of downloads: 4
Go to the top of the page
post Feb 11 2019, 02:00 PM

Posts: 5,359
Joined: 2-November 04
From: Downey, CA

I'm open to hear what others have to say, but as far as design, I would strongly recommend renaming all the "ID" fields to "ProjectID," "TaskID," "EmployeeID," etc.

Edit: Let me clarify - I'm not saying you shouldn't have ANY fields named "ID," definitely the Projects table - and any tasks /work completed link to the original projects...

This post has been edited by bakersburg9: Feb 11 2019, 02:08 PM
Attached File(s)
Attached File  ProjectID.jpg ( 38.58K )Number of downloads: 0
Go to the top of the page
post Feb 11 2019, 02:02 PM

Posts: 7
Joined: 7-February 19

I honestly think that is a good idea and something that I will most certainly will do.

Thanks !
Go to the top of the page

Custom Search

RSSSearch   Top   Lo-Fi    22nd February 2019 - 09:20 AM