Thank you Nicole_N. Please clarify a couple of things.

Are you saying that I have to run the report on ALL customers for ALL dates, then edit it in Excel? That seems to be the only way to limit the report to Active customers and make sure I am seeing all of the last invoices for those customers. It also seems like a lot of work. If I have 500 ACTIVE CUSTOMERS but only want to see the last invoice for one customer (who has 30 jobs), and I just want a list of those 30 jobs and the last invoice for each of those, is there a way to produce that? The report you describe will give me a list of 500 Customers, multiplied by all of their respective Jobs, multiplied again by all of their invoices. If I select only the one Customer I want, it gives me ALL of his Jobs, Active and Inactive, as well as all invoices for each of those Jobs. I see no way to limit the report to ACTIVE Customer/Jobs unless I select ALL Customer/Jobs. I also see no way to limit the report to the last invoice for each of those Customer/Jobs.

I have one customer who has 30 active jobs, some of whom have been in the system since the 90s, and all I want is a list of each of those 30 active jobs next to the date and number of the last invoice for each of those Jobs, a report that would fit on 1 page, instead of a report that goes for 30 or more pages. That's what my client requested, and I am trying to find a way to provide that without spending a lot of time editing an extremely long Excel spreadsheet. Can QB give me that?

I have used QB for about 30 years, and it is a wonderful tool, but it has some extremely frustrating limitations, like the inability to produce a report that breaks down invoices by dates of service. I can get a list of services by invoice, but they all show as being provided on the same date, the date of the invoice, not the date of service, which can be seen only by looking at each invoice. Like the dates of the last activity for each Customer/Job, this is information that has been stored in the QB data, so, logically, there should be a way of extracting that information, but there isn't. I have (long ago) been through a lengthy exploration of that limitation, and even suggested a modification of the program, as you suggest. With all due respect, that process seems to fall on deaf ears.

Thanks again for your help.