Word Merge Data From MS Access Options Fields

Thanks for your reply. I think I'm getting closer to the solution.
I'm thinking of doing this in VBA so that I can use this in similar
forms for other agencies. Unfortunately these agencies woun't adopt a
uniform form. They all have 90% of the same items, but the rest is
their own ideas. So for these12 items, I'm thinking of making VBA
function driven by an event like "msoOpenDocument" or "ActiveDocument"
or "CustomDocumentProperties" or "DocumentChange". Since I'm more
familiar with MS Access than MS Word, I don't know which would be a
good trigger event to activate the function. Also I'm think that on
the form I'll use fields with no properties other than an unique name
and use VBA to set the properties and formulas into each of the fields
using those unique names (aka ID). So let me focus in on a question
that you may be able to answer.

1. How can I set the properties of each field (i.e. make it a merge
field) and include the necessary formula that would be otherwise
placed inside the field directly on the form, but now all by using
VBA? I know that there must be a way to identify each individual
field by referencing its unique name (i.e. option1, option2, etc.)
Something like: Fields.Add wrdApplication.Selection.Range, "option1"

2. Which event would you recommend to trigger the function to set the
properties?

Thanks,
PC

I would start with a Word Template in which I would use Document Variable
{ DOCVARIABLE varName } fields where you want the information from the
Access database to appear. Then in your VBA Code, you would set the value
of the variables [varname] to the value from Access using

Dim NewDoc as Document
Set NewDoc = Documents.Add("templatename")
With NewDoc
.Variables("varname").Value = somethingformAccess
'etc
.Range.Fields.Update
End With

If you are creating multiple documents, you would put this inside a
For....Next loop that iterated through the records in the database, creating
a new document for each one.

I am not sure what you mean by thinking that you are getting closer to a
solution. Whichever way, you still have the issue of needing to display
something that looks like a series of radio buttons.

You should also consider whether the whole thing can be done as a report in
Access. In a number of applications, I use Access reports to produce
documents that to look at them are indistinguishable from documents produced
by Word.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP

"PC User" <pc_user DeleteThis @softhome.net> wrote in message
news:a45b7065-6da3-435a-be59-60800c88a10f@f40g2000pri.googlegroups.com...
> Thanks for your reply. I think I'm getting closer to the solution.
> I'm thinking of doing this in VBA so that I can use this in similar
> forms for other agencies. Unfortunately these agencies woun't adopt a
> uniform form. They all have 90% of the same items, but the rest is
> their own ideas. So for these12 items, I'm thinking of making VBA
> function driven by an event like "msoOpenDocument" or "ActiveDocument"
> or "CustomDocumentProperties" or "DocumentChange". Since I'm more
> familiar with MS Access than MS Word, I don't know which would be a
> good trigger event to activate the function. Also I'm think that on
> the form I'll use fields with no properties other than an unique name
> and use VBA to set the properties and formulas into each of the fields
> using those unique names (aka ID). So let me focus in on a question
> that you may be able to answer.
>
> 1. How can I set the properties of each field (i.e. make it a merge
> field) and include the necessary formula that would be otherwise
> placed inside the field directly on the form, but now all by using
> VBA? I know that there must be a way to identify each individual
> field by referencing its unique name (i.e. option1, option2, etc.)
> Something like: Fields.Add wrdApplication.Selection.Range, "option1"
>
> 2. Which event would you recommend to trigger the function to set the
> properties?
>
> Thanks,
> PC
>
>
>
>