Shellexecute to open a Word.doc - no reaction 1

[Koen Piller]

Hi,

I would like to open a word.doc in my VFP application and have therefore constructed:

DECLARE INTEGER SellExecute in Shell32.dll ;
INTEGER hhdWin, ;
STRING cAction, ;
STRING cFileName, ;
STRING cParams, ;
STRING cDir, ;
INTEGER nShowWin

lcFileName = "myWord.DOC"
= shellexecute(0,"open",lcFilename,"","",1)

And nothing, virtualy nothing, happens.
So I replaced lcFilename with

SYS(5)+SYS(2003)+"\archief\myWord.doc"

still nothing

needless to say.
- Word is installed on this PC
- Directory archief is found in my path
- File myWord.DOC resides in SYS(5)+SYS(2003)+"\archief"

What possibilities do I have to correct this unwanted behavior?

Regards,

Jockey(2)

 

[Mike Lewis]

Testing on a different PC sounds good. Let us know the result.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

 

[Olaf Doschke]

> it's interesting that when Jockey double-clicked on the file, Word was successfully opened
This is puzzling, but to me it only shows there are at least two places in the registry about file associations, that are normally in sync.
Scotts experiment of associating DOC with Wordpad and back to MS Word shows this is related, but Jockeys error shows its separate, too.

Bye, Olaf.

 

[DSummZZZ]

I may have overlooked it, but I haven't seen anyone address the actual pathing problem in the first post. SheellExecute needs to know where the file is and I have found that prefacing the filename with the path doesn't always work. It has always worked better for me to use the 'path' parameter:

DECLARE INTEGER SellExecute in Shell32.dll ;
INTEGER hhdWin, ;
STRING cAction, ;
STRING cFileName, ;
STRING cParams, ;
STRING cDir, ;
INTEGER nShowWin

lcFileName = "myWord.DOC"
[COLOR=blue]lcPath = SYS(5)+SYS(2003)+"\archief" [/color]
= shellexecute(0, "open", lcFilename, "", [COLOR=blue]lcPath[/color], 1)

-Dave Summers-

Even more Fox stuff at:

http://www.dave-summers.net/foxprolinks.htm

 

[Mike Lewis]

Dave,

This was indeed addressed right at the beginning of the thread - although it would be easy to miss, given that there have been over 40 posts so far.

Mike



__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

 

[DSummZZZ]

Hmmm. Must have skimmed right past it. My bad.

-Dave Summers-

Even more Fox stuff at:

http://www.dave-summers.net/foxprolinks.htm

 

[Koen Piller]

Hi,

Sorry, overlooked to inform about my test to open Word.doc in the same application, same document, on an other PC with shellexecute():
No problem. Works like a charm.
Remains the puzzle what made it unworkable on the first pc?
I am afraid, this will never be solved.
Anyway changed my coding to be more defensive in case someone else using this application also faces a nonworkable shellexecute() for Word.

Thanks for moral support,

Jockey(2)

 

[Tore Bleken]

I already told you. Uninstall Word365 and repair teh "normal" Word version.

 

[Scott24x7]

Jockey2,
Why can't you just reinstall the OS on the first PC, put the application back on it, and all should be fine.
Most likely your registry is baked. Mucking with the registry can be very difficult, and is beyond the scope of this forum (it's VFP, not Windows Registry forum)...
That's the simple route.
-S

Best Regards,
Scott
ATS, CDCE, CTIA, CTDC

"Everything should be made as simple as possible, and no simpler."

 

[Koen Piller]

Scott,

Will join the Windows Registry Forum, get disposed of that PC. Either or

To uninstall and re-install Word365 the route as proposed by Tore. Could be a possibility. Will check with MS first about the license.

Regards,
Jockey(2)

 

[Tore Bleken]

No, don't install Word365. Not unless you really need it....! But reinstalling it will most likely bring back the problem.