Mail Merge has a problem when run on a Vista Machine

This is driving me crazy. In my program I extract out data that I want to
merge into a Word Document, from within my program I start word and then
leave it to the user to complete the merge. This works great on XP but has
all kinds of problems with Vista. Here's what happens, word starts but the
message about running this SQL statement comes up behind access and you can't
get to it without alt ctrl del and end the Access task, this message doesn't
show up on the task bar so if your not expecting it access looks like it's
hung up.
I've modified the code to the following
apppathx = ("" & apppath & "" + "\" + "ribbonlables.txt")
DoCmd.TransferText acExportMerge, , vtable, apppathx, True
apppath = Application.CurrentProject.Path
pathnew = ("" & apppath & "" + "\" & wrddoc & "")
Set oApp = CreateObject(Class:="Word.application")
oApp.Documents.Open FileName:=pathnew
oApp.Visible = True
this now at least puts word on the task bar but I don't get the SQL message
any more and when I go to do the merge the data source is not there. I'll
point to the source and save the document but the next time I run the program
word comes up but the source is missing (it will not save the source
location). I don't know if the SQL statement is being answered with a No or
what. If anybody can help I would sure appreciate it.
I know this is quite a long question but I don't know how else to explain it.
Thanks for any help
Tom

Just found another thing with word, if I start word up and open the document
it comes up with the select * message, so my thoughts regarding the answer to
no as that is the default on the message. Now is there any way beside
editing the registries (customers would have a problem doing this) to make
the default to this message yes?
Hopefully I'll get an answer to this problem. It only happens with Vista.


"CD Tom" wrote:

This is driving me crazy. In my program I extract out data that I want to
merge into a Word Document, from within my program I start word and then
leave it to the user to complete the merge. This works great on XP but has
all kinds of problems with Vista. Here's what happens, word starts but the
message about running this SQL statement comes up behind access and you can't
get to it without alt ctrl del and end the Access task, this message doesn't
show up on the task bar so if your not expecting it access looks like it's
hung up.
I've modified the code to the following
apppathx = ("" & apppath & "" + "\" + "ribbonlables.txt")
DoCmd.TransferText acExportMerge, , vtable, apppathx, True
apppath = Application.CurrentProject.Path
pathnew = ("" & apppath & "" + "\" & wrddoc & "")
Set oApp = CreateObject(Class:="Word.application")
oApp.Documents.Open FileName:=pathnew
oApp.Visible = True
this now at least puts word on the task bar but I don't get the SQL message
any more and when I go to do the merge the data source is not there. I'll
point to the source and save the document but the next time I run the program
word comes up but the source is missing (it will not save the source
location). I don't know if the SQL statement is being answered with a No or
what. If anybody can help I would sure appreciate it.
I know this is quite a long question but I don't know how else to explain it.
Thanks for any help
Tom