Hi Ed,
Well, I've got a somewhat better idea of what you're wanting, but I think
you're labouring under several mis-apprehensions - and I'm still a little
puzzled as to your exact situation.
First, I don't understand what you mean by an "Access Report form". Is this
a form, or a report? They are not the same thing.
Second, neither a form nor a report contain a table. Both are simply
methods of displaying data from a table (or query); what looks like a table
is a set of textbox controls displaying data from the bound fields of the
underlying recordsource. You cannot "highlight the table on the report
form" because there is no such thing!
If you are prepared to do some manual cut/paste (and reformatting, if
necessary to match fonts, etc) to get the data from a and Access table/query
into a table in a Word document, you can use the SendObject method to export
the table (or query) which is the recordsource for your form/report. For
example, the following:
DoCmd.SendObject acSendTable, "tblReport", acFormatRTF, , , , , , False
will open a mail message (in your email program - Outlook, Outlook Express,
whatever) which contains only an attachment, a Word (.rtf) document named
"tblReport.rtf" containing a real (Word) table, which you can select in it's
entirety and copy/paste into your main Word document; the table borders are
resizeable, data is not truncated to fit cell sizes, etc.
If your data is in a query, change acSendTable to acSendQuery. Set the
second parameter (the string within quotes) to the name of your table or
query - whatever is the recordsource of your form/report.
After copy/paste to your document, you can just close the generated email
message without sending it. This will generate an error message (Error
2501), which you can trap and ignore in your code, if you don't want to see
it.
Maybe that's a suitable solution for you; your reply in the other thread to
MikeJohnB seems to idicate that you are willing to do some manual cut/paste
operation(s). If not, then you'll almost certainly need to go the Office
Automation path - and if you do go that way, you'll need reasonably good VBA
coding skills, and an understanding of the object models of both Access and
Word.
HTH,
Rob