missing query bug?

[JethroUK]

tired to connect a document to an access database and the window only a
shows the tables and one query (the 2 other database queries are not shown)

so i can't connect the doc to the query it needs - is this a bug?

 

[JethroUK]

Have investigated the bug - Microsoft Word won't merge with some Access
queries ?????????????

Assumed it was a software suite - You should be alright if you dont use any
criteria - stick to the simple criteria in Word only

Only been using the tool about 10 seconds and it is already falling apart at
the seems - obviously not for professional use

 

[Doug Robbins - Word MVP]

What sort of criteria are you talking about, I have used select queries
with criteria that controls which records from the table are returned by the
query as the datasource for mailmerges hundreds of the times.

--
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

 

[JethroUK©]

The query criteria is from a form e.g.

[Forms]![Form1]![Control]

query on it's own works fine - just M.S. Word mailmerge won't see it as a
datasource (doesn't even appear in the database tables/queries window as a
datasource) unless i remove the criteria - i assume the sql statement is too
complex for it

i tried removing the criteria - attaching it as a datasource - replacing the
criteria - but mailmerge doc just loses it as a datasource & of course you
can't re-attach it

i did a google and discovered that others have already noticed that word
cant/wont see some Access queries

is it possible to pass just the 'where' part of the sql statement direct to
the mailmerge doc (hence bypassing the need for a form.control to store it)?

 

[Doug Robbins - Word MVP]

I would guess that you are running up against the same "issue" that occurs
in Access when you open such a query when the Form is not open.

--
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

The query criteria is from a form e.g.

[Forms]![Form1]![Control]

query on it's own works fine - just M.S. Word mailmerge won't see it as a
datasource (doesn't even appear in the database tables/queries window as a
datasource) unless i remove the criteria - i assume the sql statement is
too
complex for it

i tried removing the criteria - attaching it as a datasource - replacing
the
criteria - but mailmerge doc just loses it as a datasource & of course you
can't re-attach it

i did a google and discovered that others have already noticed that word
cant/wont see some Access queries

is it possible to pass just the 'where' part of the sql statement direct
to
the mailmerge doc (hence bypassing the need for a form.control to store
it)?

What sort of criteria are you talking about, I have used select queries
with criteria that controls which records from the table are returned by the
query as the datasource for mailmerges hundreds of the times.

--
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

 

[JethroUK]

i've already tried it both with the form open and closed - either way the
query does not appear as a possible mailmerge datasource

the database isn't populated yet (handful records) & i seemed to remember an
option not to show empty records/recordset - that might be the problem -
would you know of such an option?

I would guess that you are running up against the same "issue" that occurs
in Access when you open such a query when the Form is not open.

--
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

The query criteria is from a form e.g.

[Forms]![Form1]![Control]

query on it's own works fine - just M.S. Word mailmerge won't see it as a
datasource (doesn't even appear in the database tables/queries window as
a
datasource) unless i remove the criteria - i assume the sql statement is
too
complex for it

i tried removing the criteria - attaching it as a datasource - replacing
the
criteria - but mailmerge doc just loses it as a datasource & of course
you
can't re-attach it

i did a google and discovered that others have already noticed that word
cant/wont see some Access queries

is it possible to pass just the 'where' part of the sql statement direct
to
the mailmerge doc (hence bypassing the need for a form.control to store
it)?

What sort of criteria are you talking about, I have used select queries
with criteria that controls which records from the table are returned by the
query as the datasource for mailmerges hundreds of the times.

--
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

Have investigated the bug - Microsoft Word won't merge with some
Access
queries ?????????????

Assumed it was a software suite - You should be alright if you dont
use
any criteria - stick to the simple criteria in Word only

Only been using the tool about 10 seconds and it is already falling apart
at the seems - obviously not for professional use



tired to connect a document to an access database and the window only
a
shows the tables and one query (the 2 other database queries are not
shown)

so i can't connect the doc to the query it needs - is this a bug?

 

[Doug Robbins - Word MVP]

From the Tools menu, select Options and then on the General tab, check the
box for "Confirm conversions at open" and then try the different connection
methods that will be offered when you attach the data source to the main
document.

--
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

i've already tried it both with the form open and closed - either way the
query does not appear as a possible mailmerge datasource

the database isn't populated yet (handful records) & i seemed to remember
an option not to show empty records/recordset - that might be the
problem - would you know of such an option?

I would guess that you are running up against the same "issue" that occurs
in Access when you open such a query when the Form is not open.

--
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

The query criteria is from a form e.g.

[Forms]![Form1]![Control]

query on it's own works fine - just M.S. Word mailmerge won't see it as
a
datasource (doesn't even appear in the database tables/queries window as
a
datasource) unless i remove the criteria - i assume the sql statement is
too
complex for it

i tried removing the criteria - attaching it as a datasource - replacing
the
criteria - but mailmerge doc just loses it as a datasource & of course
you
can't re-attach it

i did a google and discovered that others have already noticed that word
cant/wont see some Access queries

is it possible to pass just the 'where' part of the sql statement direct
to
the mailmerge doc (hence bypassing the need for a form.control to store
it)?


What sort of criteria are you talking about, I have used select
queries
with criteria that controls which records from the table are returned
by
the
query as the datasource for mailmerges hundreds of the times.

--
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

Have investigated the bug - Microsoft Word won't merge with some
Access
queries ?????????????

Assumed it was a software suite - You should be alright if you dont
use
any criteria - stick to the simple criteria in Word only

Only been using the tool about 10 seconds and it is already falling
apart
at the seems - obviously not for professional use



tired to connect a document to an access database and the window
only a
shows the tables and one query (the 2 other database queries are not
shown)

so i can't connect the doc to the query it needs - is this a bug?