G
Glen
I have button on my main switchboard that starts a RunApp macro similar to
"C:\PathToWord\Winword.exe" "C:\PathToDoc\BankLetter.doc
that looks back to Access to get a table called "Signers" to do a mail merge with BankLetter.doc
The problem is that Word seems to then start a second instance of Access and my database to get to the Signers table. So, I then have two instances of Access running, both with the same database.
Is there a way to stop this? If Access is already open, I don't want/need a second instance of Access
"C:\PathToWord\Winword.exe" "C:\PathToDoc\BankLetter.doc
that looks back to Access to get a table called "Signers" to do a mail merge with BankLetter.doc
The problem is that Word seems to then start a second instance of Access and my database to get to the Signers table. So, I then have two instances of Access running, both with the same database.
Is there a way to stop this? If Access is already open, I don't want/need a second instance of Access