There is none. At least not directly.
You need to figure out why the blanks exist in the aggregate (e.g. trace the generation of the blank record back to the recordset which causes it to be generated)) and correct the source problem.
If the aggregate is built from several sources, this can become really difficult. If it is only a couple of sources, there it is generally fairly easy.
While I would agree that you shoulnd't have blank records in table type recordsets, queries from multiple sources which do not include All of hte fields from ALL of the record sources will often include blank 'records'. this makes a good starting point for tracing the blanke in your agggregate - if the source for the aggregate includes such arrangement(s). Make "parallel" queries which include ALL Fields from ALL sources. Check the records where the fields used in the aggregate are blank. With ALL the fields present it should be easier to see where the blanks in the aggregate are generated.
MichaelRed
redmsp@erols.com
There is never time to do it right but there is always time to do it over