Limit recordset to top 1 per group

[BruceM]

Worst part was I didn't learn about it until after the initial build. I
guess it's one of those things they started doing at some point, and it
became part of the system without a deliberate plan.
Thanks again for your interest in the problem and the thought you have
devoted to helping me sort it out.

That sure does sound like an odd accounting approach, but I
guess you have it under control. Good luck with the next
problem ;-)
--
Marsh
MVP [MS Access]

A revised PO, unlike a new requisition record, starts with a PO_Number,
but
unlike a "standard" PO it has not been approved. Therefore when the
personnel who do approvals review records that need approval, they need to
see the unapproved revised POs as well as unapproved requisitions
(PO_Number
not yet assigned). Seems a cumbersome accounting approach, but that's how
they do it. The default recordset when the PO form is opened is all
records
that need at least one approval.
I see the logic of doing away with the Nz in the Where condition. I tried
your longer version that tests for equivalency and null, and it seems to
work (although I have not tested thoroughly yet).

"Marshall Barton" wrote