Help merging multiple rows into one row/concat'ing single field

[cnstarz]

In my simple database, I keep track of tasks. Each task might have multiple notes. In my report, I want it to show each task only once and I want notes concatenated somehow into a single field. For instance, my report currently looks like this:

TaskName	Task Desc	Start Date	End Date	Notes
San Antonio	Something	1/1/2011	1/2/2011	ALF
San Antonio	Something	1/1/2011	1/2/2011	Note 1
Albuquerque	ABQ Note	2/2/2012	2/3/2012	Note 2
Albuquerque	ABQ Note	2/2/2012	2/3/2012	Heartbleed
Albuquerque	ABQ Note	2/2/2012	2/3/2012	Note 1
Albuquerque	ABQ Note	2/2/2012	2/3/2012	Konami
Dallas	I hate Dallas	3/3/2013	3/4/2013	Crest
Apple	Destroy Apple.	4/4/2014	4/5/2014	OCC
Apple	Destroy Apple.	4/4/2014	4/5/2014	Peanut Butter

But I want it to look like more condensed like this:

TaskName	Task Desc	Start Date	End Date	Notes
San Antonio	Something	1/1/2011	1/2/2011	ALF, Note 1
Albuquerque	ABQ Note	2/2/012	2/3/2012	Note 2, Heartbleed, Note 1, Konami
Dallas	I hate Dallas	3/3/2013	3/4/2013	Crest
Apple	Destroy Apple.	4/4/2014	4/5/2014	OCC, Peanut Butter

How do I accomplish this? Attached is my database, just open the "Tasking Order Report" to see what I'm talking about. Thanks for your help!

[June7]

Review http://allenbrowne.com/func-concat.html

[cnstarz]

Review http://allenbrowne.com/func-concat.html

Perfect -- thanks for the link!

Although there's another problem in my database I ran into that's sort of related. In my join table (jtbTaskNotes), it only has records for tasks that have notes. However, I want the table to add a record for every Task created even if there are no notes for that task. How can I accomplish this so that I dont have to create a query that shows every Task record? Database is attached.

[June7]

I guess when record is created in tbTasks, could have code that immediately saves record to jtbTaskNotes.

But what's wrong with using a query that includes tbTasks?

[cnstarz]

Nothing wrong with the query, just figured it would be more efficient and resourceful if my database relied on one less query. I thought I had read somewhere that using outer joins weren't recommended (which is how the query works), so I was also trying to avoid that.

[June7]

I don't know why outer join would be inadvisable, never read anything like that. Use them frequently. Don't see how a db could function without them.

Then there is the argument against creating unnecessary records. This uses up file capacity more than a query statement.