One-to-Many Query, Choosing Only One Of The "Many" For Each "One"

Apologies for the way in which I describe the tables and data, I know I'm not using a very proper way to get my point across:

Table A: "tblJobs" Contains the following:
--------------------------------------------

COLUMNS:
1. JobPK (char(35))
2. LocationName (varchar(50))

DATA (csv):
6643C9C9-7618-472F-9859844AA6C0F47B, Jonesport ME
08563708-3830-4507-B3154E9C4D49C6F2, Garden City NY



Table B: "tblJobDates" contains the following data, related to the two rows above):
--------------------------------------------

COLUMNS:
1. JobPK (char(35))
2. DateData (datetime)
3. CRD (datetime, "Created Date" the date and time that the date was entered)

DATA (csv):
6643C9C9-7618-472F-9859844AA6C0F47B, 6/8/2002, 6/10/2002 12:44:58 PM
6643C9C9-7618-472F-9859844AA6C0F47B, 6/17/2002, 4/22/2002 2:07:31 PM
08563708-3830-4507-B3154E9C4D49C6F2, 6/12/2002, 6/7/2002 4:05:06 PM
08563708-3830-4507-B3154E9C4D49C6F2, 6/13/2002, 6/12/2002 11:38:22 AM

tblJobDates serves two purposes: to give us the most recently entered due date for a job, and to serve as a "repository" to track changes to the due date.


Report C: The report I want to generate does NOT provide historical information... it only serves to show the CURRENT due date for each job in the tblJobs table:
--------------------------------------------

COLUMNS:
LocationName
Due Date (alias of DateData)

OUTPUT (csv):
Jonesport ME, 6/8/2002
Garden City NY, 6/13/2002

Note that for Jonesport, an initial due date of 6/17/2002 was entered (based on the CRD). Then someone changed it so that the job was due EARLIER.

Note that for Garden City, an initial due date of 6/12/2002 was entered (based again on the CRD). Then someone changed it so that the job was due LATER.

The "most recently entered due date" is what should be reflected in my report -- just as it does above ("C")

Other Notes:

-- There are other columns of information from both tables that i would like to return, but above is the most basic form of my request. Most notably, we would need to return the JobPK in report (C).

-- A job should only appear ONCE in report (c), with it's "current" due date, regardless of the other due dates that may have been entered for that job.

-- If a job has no due date, it should not appear on the report.

-- Although not shown here, each row in (B) DOES have a unique identifier (DatePK) as well... if that helps in your solution.

-- Note that the job that is "due first" appears at the top of report (C). This allows a person looking at the report to quickly determine which job "gets priority" -- the one on top!

Okay gurus -- how should the query look that would generate the desired output in Report C?

THANKS IN ADVANCE if you even can point me in the right direction!!