Roughly speaking, there are a few ways you could approach this.

Word mailmerge would probably only be useful if all the data for a single
report exists in a single row in your database, and if all the data
(including any long text fields) is made available to Word via the ODBC
driver that comes with your database software. In that case you could
consider setting up your database as the data source for a merge and using
{ MERGEFIELD } fields to insert text data, and a nested { INCLUDEPICTURE {
MERGEFIELD picturepathnamefield } } to include the picture. Then merge to a
new document. You might also want to select the resulting document and
"unlink" all its fields as well.

You could also consider using { DATABASE } fields (use Word Tools|Customize
to enable the DATBASE toolbar and see if you can retrieve data from your
database using the Insert|Database icon. Ensure that in the last step, you
insert the data as a field). You may find that you simply can't insert data
using this approach. But if you can, as long as you only select one column
and specify that you do not want headings, Word will return plain text
rather than a table. As long as you know where to get each piece of data in
your report from you should be able to make multiple copies of your DATABASE
field, modifying the SQL in each copy to get the data you need. Inserting
the pictures would also involve a nested field using

{ INCLUDEPICTURE { DATABASE ...whatever... } }

Then select the entire document and press F9 to update all the fields. The
challenge in this approach would probably be to make it easy to change which
database, table(s) or record(s) the data would need to come from for each
report. However, there are several possible ways to do that, including the
straightforward Edit|Replace approach.

The third way would be to use VBA to get your data, and to populate each
part of the document as necessary. Since your database supports ODBC it
ought to be possible to use ADO to open it and retrieve data (using the
OLEDB provider for ODBC data sources. If your database also supports OLEDB,
it should be more straightforward). Although going along this route might
give you a lot more control (and in fact it might be the only simple way to
automate your task) there's quite a lot to learn if you haven't done this
kind of stuff before and have no resource to do it for you.

--
Peter Jamieson - Word MVP
Word MVP web site http://word.mvps.org/