-----Original Message-----
Since you cannot assign a toolbar to a query, another option might be to
create the report with *unbound* text boxes - as many as the maximum number
the query could have.
Then in the Open event of the report, assign ControlSource of each of the
needed text boxes, the Visible property of the remainder, the Left and Width
of each text box (for desired spacing/layout), the Caption of each of the
labels, the ControlSource of your GroupLevels, etc.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Reply to group, rather than allenbrowne at mvps dot org.
.You are right! I did do that but the problem arose when
the users wanted to not only see only the information that
they queried on. (that was easy), but they wanted the
fields that they queried to be the ONLY fields in the
report. In other words I had to tell the unbound fields
to have a width of 0.01 if they were null, and then tell
the populated fields to move over the null fields so that
the selected fields were next to each other in the
report. With 20 fields I can not even begin to think of
how many different combinations the users could select
when generating a report. Each selection forcing me to
script a layout for the fields. That is why I decided to
give them a query. The query will only display what they
select, and the fields will be next to one another. Can i
make a query look like a report?