B
BAC
I've got a word mail-merge main document that has worked for the last 6
months and today is giving me the above status bar message.
When I open the Word document, Access opens and I get the login screen for
my .mdw workgroup. After entering my UID & Password, I used to be prompted
for a date parameter for the underlying query..that no longer happens.
Access is open and I can get to the database window and run the query
manually. When I open Task Manager, the Application tab shows Access as
"Running" and Word as "Not Responding".
I have moved both the Access database and Word document to my local drive
(they were running on a network drive); verified that the "Enable DDE
Refresh" option is checked and the "OLE.DDE timeout (sec)" box is set for 10
seconds. The query behind the Mail Merge is an ODBC call which is active and,
as noted above, works when run in Access, but no longer runs when I open the
Word document.
I have reconstructed the query and the document from scratch, but I get the
"Waiting for ..." message after selecting the query in the Access database
(butr at least here I get beyond the .mdw.workgroup login..
Any ideas as to why this "connection" may no longer be working? I've run out
of ideas on where to look or what else to look for...The KB gave me nothing..
Thanx
months and today is giving me the above status bar message.
When I open the Word document, Access opens and I get the login screen for
my .mdw workgroup. After entering my UID & Password, I used to be prompted
for a date parameter for the underlying query..that no longer happens.
Access is open and I can get to the database window and run the query
manually. When I open Task Manager, the Application tab shows Access as
"Running" and Word as "Not Responding".
I have moved both the Access database and Word document to my local drive
(they were running on a network drive); verified that the "Enable DDE
Refresh" option is checked and the "OLE.DDE timeout (sec)" box is set for 10
seconds. The query behind the Mail Merge is an ODBC call which is active and,
as noted above, works when run in Access, but no longer runs when I open the
Word document.
I have reconstructed the query and the document from scratch, but I get the
"Waiting for ..." message after selecting the query in the Access database
(butr at least here I get beyond the .mdw.workgroup login..
Any ideas as to why this "connection" may no longer be working? I've run out
of ideas on where to look or what else to look for...The KB gave me nothing..
Thanx