Formula will not work with mail merge

[Guest]

I have a very small Access file that computes totals for money owed.

It contains one table that has information that is input by hand.

It also contains one query that pulls some of the information from that table,
including costmo1 and costmo2, and two formulas (see below).

Monthly Cost: (0+Nz([costmo1]))+(0+Nz([costmo2]))

Total Cost: [Monthly Cost]*6

The query generates everything correctly.

We use mail merge to create bills to be mailed

It has worked fine for two years. It was created in Office 2000.
We upgraded to Office 2003 and the user has used it with 2003 successfully.

All of the sudden, the Word document will not see the query.

If I change the formula for Monthly Cost to a simple thing like 2*5 and save
the query, the word document will see the query.

When I try to create a brand new mail merge document, the query still cannot
be seen with the original formula.

Can you help me?

 

[Duane Hookom]

Try this:
Monthly Cost: Val(Nz([costmo1],0)+Nz([costmo2],0))
Total Cost: Val(Nz([costmo1],0)+Nz([costmo2],0)) * 6

 

[Guest]

Hi Joan,

I will paste text from a previous post below that I think may also apply to
your case. Please post back if it doesn't resolve your issue.

(Previous post)
I'm not sure if it is the source of your problem, but many Mail Merge
problems cropped up in Office 2002 as a result of a change in the default way
that Word connects to Access. The following, an old post from Cheryl
Fischer, describes the case very well.

"Peter Jamieson, MS Word MVP, offered the following explanation and
work-around (which I found by doing a Google search on "Word mail merge does
not show all Access queries"). I tested his work-around and it works.

"This is partly a result of a change in the default way Word connects to
Access data. In Word 2000 and earlier, Word used DDE and started Access
itself. In Word 2002, Word uses OLEDB which just uses the underlying Jet
engine to get the data. The two different methods basically use different
dialogs, which "explains" your question 1. As for question 2, I do not know
why OLEDB does not show /all/ the queries. As far as I can tell, there are
two possible reasons:
a. security - e.g. if you are using a workgroup database and have set up
security differently for some queries.
b. queries that use "user defined functions", i.e. functions you have
written in Access VBA cannot be executed by OLEDB and are not presented, and
other types of query such as parameter queries will probably not work even
if you can connect to them.

A workaround is to revert to the old DDE connection mechanism - to do this,
check Word Tools|Options|General|"Confirm conversions at open" and reconnect
to the .mdb. After you have selected the .mdb in "Select Data SOurce" you
will see a dialog box listing connection methods - choose the one with
Access and DDE in it.""

If that doesn't help, you may want to try googling the Access or Word
communities specifically, using:

http://groups.google.com/group­s?hl=en&lr=&ie=UTF-8&oe=UTF-8&­group=mic...

HTH, Ted Allen

I have a very small Access file that computes totals for money owed.

It contains one table that has information that is input by hand.

It also contains one query that pulls some of the information from that table,
including costmo1 and costmo2, and two formulas (see below).

Monthly Cost: (0+Nz([costmo1]))+(0+Nz([costmo2]))

Total Cost: [Monthly Cost]*6

The query generates everything correctly.

We use mail merge to create bills to be mailed

It has worked fine for two years. It was created in Office 2000.
We upgraded to Office 2003 and the user has used it with 2003 successfully.

All of the sudden, the Word document will not see the query.

If I change the formula for Monthly Cost to a simple thing like 2*5 and save
the query, the word document will see the query.

When I try to create a brand new mail merge document, the query still cannot
be seen with the original formula.

Can you help me?

 

[Guest]

The formulas below work in the query, but I sstill cannot get the data to
merge into the document.

Try this:
Monthly Cost: Val(Nz([costmo1],0)+Nz([costmo2],0))
Total Cost: Val(Nz([costmo1],0)+Nz([costmo2],0)) * 6


--
Duane Hookom
MS Access MVP
--

I have a very small Access file that computes totals for money owed.

It contains one table that has information that is input by hand.

It also contains one query that pulls some of the information from that
table,
including costmo1 and costmo2, and two formulas (see below).

Monthly Cost: (0+Nz([costmo1]))+(0+Nz([costmo2]))

Total Cost: [Monthly Cost]*6

The query generates everything correctly.

We use mail merge to create bills to be mailed

It has worked fine for two years. It was created in Office 2000.
We upgraded to Office 2003 and the user has used it with 2003
successfully.

All of the sudden, the Word document will not see the query.

If I change the formula for Monthly Cost to a simple thing like 2*5 and
save
the query, the word document will see the query.

When I try to create a brand new mail merge document, the query still
cannot
be seen with the original formula.

Can you help me?

 

[Duane Hookom]

When perform merges to Word, I generally push the records to a separate Word
Merge format file. This gets around most merge related issues.

--
Duane Hookom
MS Access MVP
--

Hi Joan,

I will paste text from a previous post below that I think may also apply
to
your case. Please post back if it doesn't resolve your issue.

(Previous post)
I'm not sure if it is the source of your problem, but many Mail Merge
problems cropped up in Office 2002 as a result of a change in the default
way
that Word connects to Access. The following, an old post from Cheryl
Fischer, describes the case very well.

"Peter Jamieson, MS Word MVP, offered the following explanation and
work-around (which I found by doing a Google search on "Word mail merge
does
not show all Access queries"). I tested his work-around and it works.

"This is partly a result of a change in the default way Word connects to
Access data. In Word 2000 and earlier, Word used DDE and started Access
itself. In Word 2002, Word uses OLEDB which just uses the underlying Jet
engine to get the data. The two different methods basically use different
dialogs, which "explains" your question 1. As for question 2, I do not
know
why OLEDB does not show /all/ the queries. As far as I can tell, there are
two possible reasons:
a. security - e.g. if you are using a workgroup database and have set up
security differently for some queries.
b. queries that use "user defined functions", i.e. functions you have
written in Access VBA cannot be executed by OLEDB and are not presented,
and
other types of query such as parameter queries will probably not work even
if you can connect to them.

A workaround is to revert to the old DDE connection mechanism - to do
this,
check Word Tools|Options|General|"Confirm conversions at open" and
reconnect
to the .mdb. After you have selected the .mdb in "Select Data SOurce" you
will see a dialog box listing connection methods - choose the one with
Access and DDE in it.""

If that doesn't help, you may want to try googling the Access or Word
communities specifically, using:

http://groups.google.com/group­s?hl=en&lr=&ie=UTF-8&oe=UTF-8&­group=mic...

HTH, Ted Allen

I have a very small Access file that computes totals for money owed.

It contains one table that has information that is input by hand.

It also contains one query that pulls some of the information from that
table,
including costmo1 and costmo2, and two formulas (see below).

Monthly Cost: (0+Nz([costmo1]))+(0+Nz([costmo2]))

Total Cost: [Monthly Cost]*6

The query generates everything correctly.

We use mail merge to create bills to be mailed

It has worked fine for two years. It was created in Office 2000.
We upgraded to Office 2003 and the user has used it with 2003
successfully.

All of the sudden, the Word document will not see the query.

If I change the formula for Monthly Cost to a simple thing like 2*5 and
save
the query, the word document will see the query.

When I try to create a brand new mail merge document, the query still
cannot
be seen with the original formula.

Can you help me?

 

[Guest]

I think you may be right. But I do not have the dde choice.

I have tried google and could not find help.
Thanks for trying. Any other ideas.

When I try to open the data base,
my next window is select data source ... I choose new source
My choices are
SQL Server
ODBC DSN
oracle (something else installed on my machine) but not installed on the
person who usually uses this database
Other/Advanced which gives me lots of choices ... not dde

Joan

Hi Joan,

I will paste text from a previous post below that I think may also apply to
your case. Please post back if it doesn't resolve your issue.

(Previous post)
I'm not sure if it is the source of your problem, but many Mail Merge
problems cropped up in Office 2002 as a result of a change in the default way
that Word connects to Access. The following, an old post from Cheryl
Fischer, describes the case very well.

"Peter Jamieson, MS Word MVP, offered the following explanation and
work-around (which I found by doing a Google search on "Word mail merge does
not show all Access queries"). I tested his work-around and it works.

"This is partly a result of a change in the default way Word connects to
Access data. In Word 2000 and earlier, Word used DDE and started Access
itself. In Word 2002, Word uses OLEDB which just uses the underlying Jet
engine to get the data. The two different methods basically use different
dialogs, which "explains" your question 1. As for question 2, I do not know
why OLEDB does not show /all/ the queries. As far as I can tell, there are
two possible reasons:
a. security - e.g. if you are using a workgroup database and have set up
security differently for some queries.
b. queries that use "user defined functions", i.e. functions you have
written in Access VBA cannot be executed by OLEDB and are not presented, and
other types of query such as parameter queries will probably not work even
if you can connect to them.

A workaround is to revert to the old DDE connection mechanism - to do this,
check Word Tools|Options|General|"Confirm conversions at open" and reconnect
to the .mdb. After you have selected the .mdb in "Select Data SOurce" you
will see a dialog box listing connection methods - choose the one with
Access and DDE in it.""

If that doesn't help, you may want to try googling the Access or Word
communities specifically, using:

http://groups.google.com/group­s?hl=en&lr=&ie=UTF-8&oe=UTF-8&­group=mic...

HTH, Ted Allen

I have a very small Access file that computes totals for money owed.

It contains one table that has information that is input by hand.

It also contains one query that pulls some of the information from that table,
including costmo1 and costmo2, and two formulas (see below).

Monthly Cost: (0+Nz([costmo1]))+(0+Nz([costmo2]))

Total Cost: [Monthly Cost]*6

The query generates everything correctly.

We use mail merge to create bills to be mailed

It has worked fine for two years. It was created in Office 2000.
We upgraded to Office 2003 and the user has used it with 2003 successfully.

All of the sudden, the Word document will not see the query.

If I change the formula for Monthly Cost to a simple thing like 2*5 and save
the query, the word document will see the query.

When I try to create a brand new mail merge document, the query still cannot
be seen with the original formula.

Can you help me?

 

[Guest]

Hmm, I don't know what would cause DDE to not show, I'm sure that could be
any number of things related to a bad install, corrupted file, etc.

In addition to looking at trying to push the records from Access as Duane
mentioned, another possibility that you may want to consider is to just
append the records to a temporary table and use that as the data source for
the mail merge.

DDE is rather slow sometimes anyway, so the temp table may work out better
for you.

I don't really do a lot of Mail Merging, so I can't really describe in
detail how to use Duane's method. I have used VBA code in Access to merge
data from a single Access record into a Word doc using bookmarks, (it's not
very complicated if you are familiar with VBA) but I haven't done anything
like that to create merge documents from an entire recordset. Normally I
just use the ODBC connection for multi-record merges and use a temp table if
necessary.

I did see in a post once that someone claimed that if they created a
standard select query from one of their queries that ODBC could not see, it
would show up and they could use that. I'm not sure if that is really the
case, but you may want to give it a try.

HTH, Ted Allen

I think you may be right. But I do not have the dde choice.

I have tried google and could not find help.
Thanks for trying. Any other ideas.

When I try to open the data base,
my next window is select data source ... I choose new source
My choices are
SQL Server
ODBC DSN
oracle (something else installed on my machine) but not installed on the
person who usually uses this database
Other/Advanced which gives me lots of choices ... not dde

Joan

Hi Joan,

I will paste text from a previous post below that I think may also apply to
your case. Please post back if it doesn't resolve your issue.

(Previous post)
I'm not sure if it is the source of your problem, but many Mail Merge
problems cropped up in Office 2002 as a result of a change in the default way
that Word connects to Access. The following, an old post from Cheryl
Fischer, describes the case very well.

"Peter Jamieson, MS Word MVP, offered the following explanation and
work-around (which I found by doing a Google search on "Word mail merge does
not show all Access queries"). I tested his work-around and it works.

"This is partly a result of a change in the default way Word connects to
Access data. In Word 2000 and earlier, Word used DDE and started Access
itself. In Word 2002, Word uses OLEDB which just uses the underlying Jet
engine to get the data. The two different methods basically use different
dialogs, which "explains" your question 1. As for question 2, I do not know
why OLEDB does not show /all/ the queries. As far as I can tell, there are
two possible reasons:
a. security - e.g. if you are using a workgroup database and have set up
security differently for some queries.
b. queries that use "user defined functions", i.e. functions you have
written in Access VBA cannot be executed by OLEDB and are not presented, and
other types of query such as parameter queries will probably not work even
if you can connect to them.

A workaround is to revert to the old DDE connection mechanism - to do this,
check Word Tools|Options|General|"Confirm conversions at open" and reconnect
to the .mdb. After you have selected the .mdb in "Select Data SOurce" you
will see a dialog box listing connection methods - choose the one with
Access and DDE in it.""

If that doesn't help, you may want to try googling the Access or Word
communities specifically, using:

http://groups.google.com/group­s?hl=en&lr=&ie=UTF-8&oe=UTF-8&­group=mic...

HTH, Ted Allen

I have a very small Access file that computes totals for money owed.

It contains one table that has information that is input by hand.

It also contains one query that pulls some of the information from that table,
including costmo1 and costmo2, and two formulas (see below).

Monthly Cost: (0+Nz([costmo1]))+(0+Nz([costmo2]))

Total Cost: [Monthly Cost]*6

The query generates everything correctly.

We use mail merge to create bills to be mailed

It has worked fine for two years. It was created in Office 2000.
We upgraded to Office 2003 and the user has used it with 2003 successfully.

All of the sudden, the Word document will not see the query.

If I change the formula for Monthly Cost to a simple thing like 2*5 and save
the query, the word document will see the query.

When I try to create a brand new mail merge document, the query still cannot
be seen with the original formula.

Can you help me?

 

[Guest]

I do not think it is a bad install ... I get the same options on three
different machines.

How do I append to a table?

Joan

Hmm, I don't know what would cause DDE to not show, I'm sure that could be
any number of things related to a bad install, corrupted file, etc.

In addition to looking at trying to push the records from Access as Duane
mentioned, another possibility that you may want to consider is to just
append the records to a temporary table and use that as the data source for
the mail merge.

DDE is rather slow sometimes anyway, so the temp table may work out better
for you.

I don't really do a lot of Mail Merging, so I can't really describe in
detail how to use Duane's method. I have used VBA code in Access to merge
data from a single Access record into a Word doc using bookmarks, (it's not
very complicated if you are familiar with VBA) but I haven't done anything
like that to create merge documents from an entire recordset. Normally I
just use the ODBC connection for multi-record merges and use a temp table if
necessary.

I did see in a post once that someone claimed that if they created a
standard select query from one of their queries that ODBC could not see, it
would show up and they could use that. I'm not sure if that is really the
case, but you may want to give it a try.

HTH, Ted Allen

I think you may be right. But I do not have the dde choice.

I have tried google and could not find help.
Thanks for trying. Any other ideas.

When I try to open the data base,
my next window is select data source ... I choose new source
My choices are
SQL Server
ODBC DSN
oracle (something else installed on my machine) but not installed on the
person who usually uses this database
Other/Advanced which gives me lots of choices ... not dde

Joan

Hi Joan,

I will paste text from a previous post below that I think may also apply to
your case. Please post back if it doesn't resolve your issue.

(Previous post)
I'm not sure if it is the source of your problem, but many Mail Merge
problems cropped up in Office 2002 as a result of a change in the default way
that Word connects to Access. The following, an old post from Cheryl
Fischer, describes the case very well.

"Peter Jamieson, MS Word MVP, offered the following explanation and
work-around (which I found by doing a Google search on "Word mail merge does
not show all Access queries"). I tested his work-around and it works.

"This is partly a result of a change in the default way Word connects to
Access data. In Word 2000 and earlier, Word used DDE and started Access
itself. In Word 2002, Word uses OLEDB which just uses the underlying Jet
engine to get the data. The two different methods basically use different
dialogs, which "explains" your question 1. As for question 2, I do not know
why OLEDB does not show /all/ the queries. As far as I can tell, there are
two possible reasons:
a. security - e.g. if you are using a workgroup database and have set up
security differently for some queries.
b. queries that use "user defined functions", i.e. functions you have
written in Access VBA cannot be executed by OLEDB and are not presented, and
other types of query such as parameter queries will probably not work even
if you can connect to them.

A workaround is to revert to the old DDE connection mechanism - to do this,
check Word Tools|Options|General|"Confirm conversions at open" and reconnect
to the .mdb. After you have selected the .mdb in "Select Data SOurce" you
will see a dialog box listing connection methods - choose the one with
Access and DDE in it.""

If that doesn't help, you may want to try googling the Access or Word
communities specifically, using:

http://groups.google.com/group­s?hl=en&lr=&ie=UTF-8&oe=UTF-8&­group=mic...

HTH, Ted Allen



:

I have a very small Access file that computes totals for money owed.

It contains one table that has information that is input by hand.

It also contains one query that pulls some of the information from that table,
including costmo1 and costmo2, and two formulas (see below).

Monthly Cost: (0+Nz([costmo1]))+(0+Nz([costmo2]))

Total Cost: [Monthly Cost]*6

The query generates everything correctly.

We use mail merge to create bills to be mailed

It has worked fine for two years. It was created in Office 2000.
We upgraded to Office 2003 and the user has used it with 2003 successfully.

All of the sudden, the Word document will not see the query.

If I change the formula for Monthly Cost to a simple thing like 2*5 and save
the query, the word document will see the query.

When I try to create a brand new mail merge document, the query still cannot
be seen with the original formula.

Can you help me?

 

[Guest]

How do I push the records to a separate Word Merge format file?

When perform merges to Word, I generally push the records to a separate Word
Merge format file. This gets around most merge related issues.

--
Duane Hookom
MS Access MVP
--

Hi Joan,

I will paste text from a previous post below that I think may also apply
to
your case. Please post back if it doesn't resolve your issue.

(Previous post)
I'm not sure if it is the source of your problem, but many Mail Merge
problems cropped up in Office 2002 as a result of a change in the default
way
that Word connects to Access. The following, an old post from Cheryl
Fischer, describes the case very well.

"Peter Jamieson, MS Word MVP, offered the following explanation and
work-around (which I found by doing a Google search on "Word mail merge
does
not show all Access queries"). I tested his work-around and it works.

"This is partly a result of a change in the default way Word connects to
Access data. In Word 2000 and earlier, Word used DDE and started Access
itself. In Word 2002, Word uses OLEDB which just uses the underlying Jet
engine to get the data. The two different methods basically use different
dialogs, which "explains" your question 1. As for question 2, I do not
know
why OLEDB does not show /all/ the queries. As far as I can tell, there are
two possible reasons:
a. security - e.g. if you are using a workgroup database and have set up
security differently for some queries.
b. queries that use "user defined functions", i.e. functions you have
written in Access VBA cannot be executed by OLEDB and are not presented,
and
other types of query such as parameter queries will probably not work even
if you can connect to them.

A workaround is to revert to the old DDE connection mechanism - to do
this,
check Word Tools|Options|General|"Confirm conversions at open" and
reconnect
to the .mdb. After you have selected the .mdb in "Select Data SOurce" you
will see a dialog box listing connection methods - choose the one with
Access and DDE in it.""

If that doesn't help, you may want to try googling the Access or Word
communities specifically, using:

http://groups.google.com/group­s?hl=en&lr=&ie=UTF-8&oe=UTF-8&­group=mic...

HTH, Ted Allen

I have a very small Access file that computes totals for money owed.

It contains one table that has information that is input by hand.

It also contains one query that pulls some of the information from that
table,
including costmo1 and costmo2, and two formulas (see below).

Monthly Cost: (0+Nz([costmo1]))+(0+Nz([costmo2]))

Total Cost: [Monthly Cost]*6

The query generates everything correctly.

We use mail merge to create bills to be mailed

It has worked fine for two years. It was created in Office 2000.
We upgraded to Office 2003 and the user has used it with 2003
successfully.

All of the sudden, the Word document will not see the query.

If I change the formula for Monthly Cost to a simple thing like 2*5 and
save
the query, the word document will see the query.

When I try to create a brand new mail merge document, the query still
cannot
be seen with the original formula.

Can you help me?

 

[Duane Hookom]

Choose File->Export. There is code that does this in the Query By Form
applet at http://www.rogersaccesslibrary.com/OtherLibraries.asp#Hookom,Duane

--
Duane Hookom
MS Access MVP

How do I push the records to a separate Word Merge format file?

When perform merges to Word, I generally push the records to a separate
Word
Merge format file. This gets around most merge related issues.

--
Duane Hookom
MS Access MVP
--

Hi Joan,

I will paste text from a previous post below that I think may also
apply
to
your case. Please post back if it doesn't resolve your issue.

(Previous post)
I'm not sure if it is the source of your problem, but many Mail Merge
problems cropped up in Office 2002 as a result of a change in the
default
way
that Word connects to Access. The following, an old post from Cheryl
Fischer, describes the case very well.

"Peter Jamieson, MS Word MVP, offered the following explanation and
work-around (which I found by doing a Google search on "Word mail merge
does
not show all Access queries"). I tested his work-around and it works.

"This is partly a result of a change in the default way Word connects
to
Access data. In Word 2000 and earlier, Word used DDE and started Access
itself. In Word 2002, Word uses OLEDB which just uses the underlying
Jet
engine to get the data. The two different methods basically use
different
dialogs, which "explains" your question 1. As for question 2, I do not
know
why OLEDB does not show /all/ the queries. As far as I can tell, there
are
two possible reasons:
a. security - e.g. if you are using a workgroup database and have set
up
security differently for some queries.
b. queries that use "user defined functions", i.e. functions you have
written in Access VBA cannot be executed by OLEDB and are not
presented,
and
other types of query such as parameter queries will probably not work
even
if you can connect to them.

A workaround is to revert to the old DDE connection mechanism - to do
this,
check Word Tools|Options|General|"Confirm conversions at open" and
reconnect
to the .mdb. After you have selected the .mdb in "Select Data SOurce"
you
will see a dialog box listing connection methods - choose the one with
Access and DDE in it.""

If that doesn't help, you may want to try googling the Access or Word
communities specifically, using:

http://groups.google.com/group­s?hl=en&lr=&ie=UTF-8&oe=UTF-8&­group=mic...

HTH, Ted Allen



:

I have a very small Access file that computes totals for money owed.

It contains one table that has information that is input by hand.

It also contains one query that pulls some of the information from
that
table,
including costmo1 and costmo2, and two formulas (see below).

Monthly Cost: (0+Nz([costmo1]))+(0+Nz([costmo2]))

Total Cost: [Monthly Cost]*6

The query generates everything correctly.

We use mail merge to create bills to be mailed

It has worked fine for two years. It was created in Office 2000.
We upgraded to Office 2003 and the user has used it with 2003
successfully.

All of the sudden, the Word document will not see the query.

If I change the formula for Monthly Cost to a simple thing like 2*5
and
save
the query, the word document will see the query.

When I try to create a brand new mail merge document, the query still
cannot
be seen with the original formula.

Can you help me?

 

[Guest]

Hi Joan,

Initially you would actually want to create the table using a make table
query (I'm assuming that you are using the query builder). To do that, go to
the Menu under Query and change the query to a Make-Table query. Access will
then prompt you for the table name that you want to create. Then, to run the
query, just click the button with an exclamation point, or close it and
double-click it in the query window. This will create your table based on
the initial select query.

Then, you may want to look at the field structure of the new table to make
sure that they are all the type that you would want.

The reason that I mentioned the append query before rather than the make
table query, is that if this is a process that you want to repeat, it is
often better to use delete and append queries from that point on, rather than
rerunning the make table query. Deleting and Appending records from a table
will leave the table structure unchanged (they only affect the records), but
running a make-table query will destroy the entire table structure and
replace it with the new table (it deletes the entire table and creates a new
one). Often, you may want to tweak the field structure of the table, or
create indexes, but you would have to redo those steps each time if you use
the make-table query beyond the initial time.

Of course, if this is a one-time thing, or if you don't find any need to
modify the table structure produced by the make-table query, you could just
continue to run those in the future.

By the way, regarding the DDE, I'm far from an expert on that, but I would
assume that either it was not installed on the machines (if that is
possible), or you may all have a common software program that damaged it, or
something similar along those lines. I have seen posts before related to DDE
where it disappeared after installing new software. As I mentioned
previously though, even when I used it I found it slow and ended up just
making a temp table for the query anyway.

You may want to try Duane's method for pushing the records from Access first
though, it sounds like it may be less work.

HTH, Ted Allen

I do not think it is a bad install ... I get the same options on three
different machines.

How do I append to a table?

Joan

Hmm, I don't know what would cause DDE to not show, I'm sure that could be
any number of things related to a bad install, corrupted file, etc.

In addition to looking at trying to push the records from Access as Duane
mentioned, another possibility that you may want to consider is to just
append the records to a temporary table and use that as the data source for
the mail merge.

DDE is rather slow sometimes anyway, so the temp table may work out better
for you.

I don't really do a lot of Mail Merging, so I can't really describe in
detail how to use Duane's method. I have used VBA code in Access to merge
data from a single Access record into a Word doc using bookmarks, (it's not
very complicated if you are familiar with VBA) but I haven't done anything
like that to create merge documents from an entire recordset. Normally I
just use the ODBC connection for multi-record merges and use a temp table if
necessary.

I did see in a post once that someone claimed that if they created a
standard select query from one of their queries that ODBC could not see, it
would show up and they could use that. I'm not sure if that is really the
case, but you may want to give it a try.

HTH, Ted Allen

I think you may be right. But I do not have the dde choice.

I have tried google and could not find help.
Thanks for trying. Any other ideas.

When I try to open the data base,
my next window is select data source ... I choose new source
My choices are
SQL Server
ODBC DSN
oracle (something else installed on my machine) but not installed on the
person who usually uses this database
Other/Advanced which gives me lots of choices ... not dde

Joan

:

Hi Joan,

I will paste text from a previous post below that I think may also apply to
your case. Please post back if it doesn't resolve your issue.

(Previous post)
I'm not sure if it is the source of your problem, but many Mail Merge
problems cropped up in Office 2002 as a result of a change in the default way
that Word connects to Access. The following, an old post from Cheryl
Fischer, describes the case very well.

"Peter Jamieson, MS Word MVP, offered the following explanation and
work-around (which I found by doing a Google search on "Word mail merge does
not show all Access queries"). I tested his work-around and it works.

"This is partly a result of a change in the default way Word connects to
Access data. In Word 2000 and earlier, Word used DDE and started Access
itself. In Word 2002, Word uses OLEDB which just uses the underlying Jet
engine to get the data. The two different methods basically use different
dialogs, which "explains" your question 1. As for question 2, I do not know
why OLEDB does not show /all/ the queries. As far as I can tell, there are
two possible reasons:
a. security - e.g. if you are using a workgroup database and have set up
security differently for some queries.
b. queries that use "user defined functions", i.e. functions you have
written in Access VBA cannot be executed by OLEDB and are not presented, and
other types of query such as parameter queries will probably not work even
if you can connect to them.

A workaround is to revert to the old DDE connection mechanism - to do this,
check Word Tools|Options|General|"Confirm conversions at open" and reconnect
to the .mdb. After you have selected the .mdb in "Select Data SOurce" you
will see a dialog box listing connection methods - choose the one with
Access and DDE in it.""

If that doesn't help, you may want to try googling the Access or Word
communities specifically, using:

http://groups.google.com/group­s?hl=en&lr=&ie=UTF-8&oe=UTF-8&­group=mic...

HTH, Ted Allen



:

I have a very small Access file that computes totals for money owed.

It contains one table that has information that is input by hand.

It also contains one query that pulls some of the information from that table,
including costmo1 and costmo2, and two formulas (see below).

Monthly Cost: (0+Nz([costmo1]))+(0+Nz([costmo2]))

Total Cost: [Monthly Cost]*6

The query generates everything correctly.

We use mail merge to create bills to be mailed

It has worked fine for two years. It was created in Office 2000.
We upgraded to Office 2003 and the user has used it with 2003 successfully.

All of the sudden, the Word document will not see the query.

If I change the formula for Monthly Cost to a simple thing like 2*5 and save
the query, the word document will see the query.

When I try to create a brand new mail merge document, the query still cannot
be seen with the original formula.

Can you help me?