First, assuming the current selected table/cursor is "CARDT", then the condition !EOF('CardT') isn't needed - it's implied.
In general, I've found that it's ultimately easier to pre-process the data and let the report work off a virtual "flat file". In this case consider an SQL Select (or a Local View if you're dealling with millions of records) of the appropriate records and feed the resultant record set to the report.
A concrete example could be given if more information on what code directly proceeds the REPORT statement. Like what table is selected, how and what relationship is established between CarsT and Postr and if any other tables (fields) and relationships are involved in the data on the report form.
Rick