I'm not sure how your query is currently calculating the
max, so I'm not sure what the best way would be, but
here's my best guess.
My guess is that you are grouping the records of a table,
and you have a field that is taking the max of one of the
table's fields. Then, the problem is that there aren't
any records for some of the records in your form (which
is grouped by vehicle ID or something similar).
If that is the case, you could modify the query so that
the vehicles table (or whatever table would provide the
same group of records that your form is using) is also
included (linked by vehicle ID or something like that).
For the relationship, you would set the join so that the
vehicles table is driving the relationship (Include all
records from tblvehicles and only those from tblusage
that match). Then you could group by the vehicle ID (or
again, whatever would match your form records 1:1) and
calc the max of the usage field. If there is not a match
in the usage table, the field would be blank (null) if
not, the max would be listed. But, you would have a
record for all form records.
This would probably solve your problem as it is. But, if
you wanted to change the nulls to 0's you could use an
iif statement in another field in the query to something
like "iif(isnull([maxofusage])=true,0,[maxofusage])"
Of course, I have had to make some assumptions about your
query and database structure so I'm not sure if this
would work. Maybe it will give you some ideas though.