I don't know why this happens but I couldn't quite understand exactly what
is happening either. Is it...
You have a table in SQL Server 2000.
Then you use a make table query in Access to create a table in Access.
Then you use that table as the data source for the merge?
Or are you managing to use the Make table query as the data source for the
merge (something I do not seem to be able to do here)?
Unless you have a very good reason to use the route you're using, I suppose
I would just try various other approaches to getting the data, e.g.
a. try a different connection method (check Word
Tools|Options|General|"Confirm conversion at open", go through the
connection process again, and see if using another method makes it work)
b. instead of using a make table query, simply link the Access table to the
SQL Server data, and write an Access query to query that data if you need to
filter the data in some way
c. get the data directly from SQL Server, either directly from the table,
or if necessary, using a view.
Peter Jamieson
> Hello
>
[quoted text clipped - 29 lines]
>
> Denise Crawley
Denise - 01 Jun 2005 11:51 GMT
Thanks for your reply, Peter. I tried a couple of difference connections
and one of them worked perfectly.
Just to clarify:-
We have a table in SQL Server
We have a linked table in Access
We run a Make Table query within Access, which produces a table in Access
This table is used for the mailmerge.
We needed to be able to filter the data as there are 10,500 records in the
main table, but often we only need to pull a dozen of these.
I used the connection 'MS Access databases via DDE (*.mdb, *.mde)', as
opposed to 'MS Access database via ODBC (*.mdb)', which the user had been
using. The connection via DDE worked.
Thanks again for your help.
Denise
> I don't know why this happens but I couldn't quite understand exactly what
> is happening either. Is it...
[quoted text clipped - 52 lines]
>>
>> Denise Crawley