Open new instance of Word from mdb.

[DaveS]

Hi! I need help opening a Word document from within an Access 2000/XP
mdb. I'm using Shell to open the document, but the Access code
continues to run past the Shell statement.

What I need is the ability to stop the code from executing until the
Word doc is closed. Additionally, I need the ability for a new instance
of Word to be created instead of opening the doc an instance of Word
that may already be open.

If you have any thoughts on this, I'd love to hear from you!! I've been
pulling my hair out on this one!

TIA,

DaveS

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Tom van Stiphout]

On 04 Aug 2004 13:55:01 GMT, DaveS <an*******@devdex.com> wrote:

Put a Stop instruction after the Shell line :-)

What you want to do is called Automation. It all starts with
CreateObject("Word.Application"). There are MANY resources on the
Internet, including this one:
http://www.mvps.org/access/modules/mdl0006.htm

Also note: perform a FULL installation of Word, so you will get the
help file that documents Word's object model.

-Tom.

Hi! I need help opening a Word document from within an Access 2000/XP
mdb. I'm using Shell to open the document, but the Access code
continues to run past the Shell statement.

What I need is the ability to stop the code from executing until the
Word doc is closed. Additionally, I need the ability for a new instance
of Word to be created instead of opening the doc an instance of Word
that may already be open.

If you have any thoughts on this, I'd love to hear from you!! I've been
pulling my hair out on this one!

TIA,

DaveS

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[asdfg2k]

On 04 Aug 2004 13:55:01 GMT, DaveS <an*******@devdex.com> wrote:

Hi! I need help opening a Word document from within an Access 2000/XP
mdb. I'm using Shell to open the document, but the Access code
continues to run past the Shell statement.

What I need is the ability to stop the code from executing until the
Word doc is closed. Additionally, I need the ability for a new instance
of Word to be created instead of opening the doc an instance of Word
that may already be open.

If you have any thoughts on this, I'd love to hear from you!! I've been
pulling my hair out on this one!

In addition to what Tom has posted, look at this for waiting the
Access application:

http://www.mvps.org/access/api/api0004.htm

paul

[DaveS]

Thanks, Paul!

Now what I need is a method of creating a NEW instance of Word every
time a doc is opened instead of opening the doc into Word if it's
already open.

Shelling out to Word seems to open Word only if it's not already open.
If it is already open, it opens the document in the currently open
instance of Word.

---------------------------
Unfortunately, OLE Automation does not seem to be the answer here,
either...

TIA,

DaveS

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[asdfg2k]

On 04 Aug 2004 19:24:51 GMT, DaveS <an*******@devdex.com> wrote:

Thanks, Paul!

Now what I need is a method of creating a NEW instance of Word every
time a doc is opened instead of opening the doc into Word if it's
already open.

Shelling out to Word seems to open Word only if it's not already open.
If it is already open, it opens the document in the currently open
instance of Word.

I suspect that the line:

..dwFlags = STARTF_USESHOWWINDOW

needs to be modified to reflect that the process must be opened in a
new window, rather than in an already existing one.

I don't know enough about the API being called to confidently identify
how to modify it, though. A little googling turned up this page,
though:

http://www.mentalis.org/apilist/CreateProcess.shtml

which might be helpful. It seems to indicate that if you set the:

CREATE_NEW_CONSOLE flag is might work.

Maybe somebody who is familiar with the API in question can indicate
whether this is close.

ringo