> On Aug 19, 2021, at 10:31 AM, Rich Shepard <rshepard@xxxxxxxxxxxxxxx> wrote: > > On Thu, 19 Aug 2021, Rob Sargent wrote: > >> Did you try David J’s suggestion? or maybe > > Rob, > > Yes. > >> select person_nbr, max(next_contact) group by person_nbr where >> next_contact < now(); > >> A table with person_nbr (pk), next_contact would make this much easier. >> Seems to me a person can only have one next-contact? (as opposed to all >> future_contact) > > The peoples table has person_nbr as the PK. The contacts table has multiple > rows for all contacts with that person_nbr. The contacts table has a > multicolum PK: person_nbr and contact_date as there is only one contact on > any given day for that person. > > HTH, > > Rich > Yeah, but my quibble is the the table you described up-thread. Your contact table contains next_contact? I think that column should be normalized out. Using David’s trick as a CTE should be descent starting point for you ultimate result? > >
