mail merge

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am having an interesting problem with mail merge. I have a query which
will not show up on the mail merge window. I see other tables and queries
but not the one I am looking for. So experimenting around I removed all of
the criteria (i.e. looking for a specific month [month (mm)] in the criteria
box) When doing so the query is now visible from word however reinserting
them causes word to bug out giving me the error of 'This operation cannot be
completed because of dialog or database engine failures. Please try again
later.’ Not liking to give up I tried to create a odc connection to the
database. This almost worked well except that none of the information
carried over from word. Not quite sure why this is happening. This has not
happened in previous versions of word or access. Any assistance would be
greatly appreciated.
 
Hi,

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




Problems with mail merge queries said:
I am having an interesting problem with mail merge. I have a query which
will not show up on the mail merge window. I see other tables and queries
but not the one I am looking for. So experimenting around I removed all of
the criteria (i.e. looking for a specific month [month (mm)] in the criteria
box) When doing so the query is now visible from word however reinserting
them causes word to bug out giving me the error of 'This operation cannot be
completed because of dialog or database engine failures. Please try again
later.’ Not liking to give up I tried to create a odc connection to the
database. This almost worked well except that none of the information
carried over from word. Not quite sure why this is happening. This has not
happened in previous versions of word or access. Any assistance would be
greatly appreciated.
 
Splendid, the advice you game worked perfectly. Thank-you very much for your
help.


Ted Allen said:
Hi,

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




Problems with mail merge queries said:
I am having an interesting problem with mail merge. I have a query which
will not show up on the mail merge window. I see other tables and queries
but not the one I am looking for. So experimenting around I removed all of
the criteria (i.e. looking for a specific month [month (mm)] in the criteria
box) When doing so the query is now visible from word however reinserting
them causes word to bug out giving me the error of 'This operation cannot be
completed because of dialog or database engine failures. Please try again
later.’ Not liking to give up I tried to create a odc connection to the
database. This almost worked well except that none of the information
carried over from word. Not quite sure why this is happening. This has not
happened in previous versions of word or access. Any assistance would be
greatly appreciated.
 
My pleasure, glad it helped.

menscandidus said:
Splendid, the advice you game worked perfectly. Thank-you very much for your
help.


Ted Allen said:
Hi,

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




Problems with mail merge queries said:
I am having an interesting problem with mail merge. I have a query which
will not show up on the mail merge window. I see other tables and queries
but not the one I am looking for. So experimenting around I removed all of
the criteria (i.e. looking for a specific month [month (mm)] in the criteria
box) When doing so the query is now visible from word however reinserting
them causes word to bug out giving me the error of 'This operation cannot be
completed because of dialog or database engine failures. Please try again
later.’ Not liking to give up I tried to create a odc connection to the
database. This almost worked well except that none of the information
carried over from word. Not quite sure why this is happening. This has not
happened in previous versions of word or access. Any assistance would be
greatly appreciated.
 
Thanks Ted.

The solution worked perfectly for me as well. I was running into an issue
with a query that worked fine on connecting with Word, until I added two
calculated fields. Then I could not "see" the query from within Word, until
I made the change you noted...

Ted Allen said:
Hi,

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




Problems with mail merge queries said:
I am having an interesting problem with mail merge. I have a query which
will not show up on the mail merge window. I see other tables and queries
but not the one I am looking for. So experimenting around I removed all of
the criteria (i.e. looking for a specific month [month (mm)] in the criteria
box) When doing so the query is now visible from word however reinserting
them causes word to bug out giving me the error of 'This operation cannot be
completed because of dialog or database engine failures. Please try again
later.’ Not liking to give up I tried to create a odc connection to the
database. This almost worked well except that none of the information
carried over from word. Not quite sure why this is happening. This has not
happened in previous versions of word or access. Any assistance would be
greatly appreciated.
 
Back
Top