Runwin and Launching Docs (None Specified)
At 25 MAR 1998 11:53:58PM Dsig (SigSolutions) wrote:
I am having a problem which I hope someone has figured ways around.
I wish to launch Word with a word doc.
This dos not work:
Rtn=Utility("RUNWIN", "C:\MYDOCU~1\BUSINESS\RESUME.DOC","")
But this does:
Rtn=Utility("RUNWIN", "C:\SIMPLE~1\PROGRAM\OILOGON.BMP","")
and this
Rtn=Utility("RUNWIN", "C:\SIMPLE~1\PROGRAM\ACTVCODE.TXT","")
Now this all worked before in Word95 but now using Word97 all this are not equal.
I have found that I can do:
Rtn=Utility("RUNWIN", "C:\PROGRA~1\MICROS~2\OFFICE\WINWORD.EXE C:\MYDOCU~1\BUSINESS\RESUME.DOC","")
but of course this means that all installations will have to have winword in the same place.
SO .. what seems to be wrong with the registry? Can anyone duplicate this AND any ideas how to get around this?
dsig
David Tod Sigafoos ~ SigSolutions
[email protected] cis:70302,77 voice:503-639-8080
At 26 MAR 1998 10:46AM Dave wrote:
David,
x=utility('RUNWIN','C:\WINDOWS\PERSONAL\LD.DOC',
) This worked for me. I am using OI 3.5, WIN 95 and office 97. Are your associations set right for word docs? IE the icon for a word file next to the file name? Could you try it form another machine? -DaveRevelation </QUOTE> —- === At 26 MAR 1998 11:58AM DSig (SigSolutions) wrote: === <QUOTE>]Are your associations set right for word docs? IE the icon for a word file next to the file name? Explorer shows the W icon. ExplorerPlus that I use shows the W icon. ]Could you try it form another machine? The same problem happens on another machine with the same OI. That is what makes me suspicious of OI. BUT then how could it launch PAINT etc? Dsig David Tod Sigafoos ~ SigSolutions [email protected] cis: 70302,77 voice: 503-639-8080 </QUOTE> —- === At 26 MAR 1998 12:03PM DSig (SigSolutions) wrote: === <QUOTE>On second thought .. Could you create a directory structure similar to mine in the example for your document. C:\My Documents\Business\xyz.doc OR could it be a combination of the long filename for the document and the long file name for the WORD? Dsig David Tod Sigafoos ~ SigSolutions [email protected] cis: 70302,77 voice: 503-639-8080 </QUOTE> —- === At 26 MAR 1998 01:23PM Dave wrote: === <QUOTE>]Explorer shows the W icon. ExplorerPlus that I use shows the W icon. If you go to the view menu choice in exploer or "my computer" then the options and check the file type does it "say opens with winword." -DaveRevelation </QUOTE> —- === At 26 MAR 1998 01:35PM David Pociu wrote: === <QUOTE>I was able to duplicate DSig's problem and I think I know what causes it. I put a document (Invoice.doc) in the root directory. I then used the following code. x=utility('RUNWIN', "C:\INVOICE.DOC" ,
)The value of x after the Utility function was executed was (with field numbers in enclosed in ):
C:\Program Files\Microsoft Office\Office\Winword.exe c:\Invoice.doc
2
0
0
So looks like it finds where the Office files are. My guess is that it does not know how to interpret the directory name over 8 characters and with enclosed spaces.
At 26 MAR 1998 03:42PM Dave wrote:
x=utility('RUNWIN','C:\thisislongerthan8\LD.DOC',
) x=utility('RUNWIN','C:\thisis~1\LD.DOC',
)Both of these worked for me.
However with a space in the directory name it does not work.
x=utility('RUNWIN','C:\thisislonger than8\LD.DOC','')
DaveRevelation
At 26 MAR 1998 04:03PM David Pociu wrote:
So the question is:
Since Windows will return the path to the EXE with spaces in it if there are any, where does the responsibility reside?
1. With the developer who will intercept the result (after the fact) correct the spacing problem somehow and re-submit the command line
2. With RevSoft who will find a way for Utility( "RUNWIN", ..) to co-exist with spaces in the directory and file names (assuming it's a RevSoft problem and not a 16/32 bit problem that you cannot do anything about)
Any ideas ?
At 27 MAR 1998 11:42PM DSig (SigSolutions) wrote:
Dave,
Yes .. DOC shows as opening with Winword
DSig
David Tod Sigafoos ~ SigSOlutions
[email protected] cis:70302,77 voice:503-639-8080
At 27 MAR 1998 11:49PM David Sigafoos wrote:
Dave,
I moved 'bankone.doc' to root of c. It still did not launch. Is it possible that the problem is that winword is in c:\program files\msoffice thus hitting the 'space' you note?
DSig
David Tod Sigafoos ~ SigSOlutions
[email protected] cis:70302,77 voice:503-639-8080
At 27 MAR 1998 11:53PM David Sigafoos wrote:
David ..
I have not followed on your testing yet but wouldn't paint which is in Program Files/accessories also have the same problem?
I will try this out later.
As you I also placed a doc file on the root with same results. I 'believe' that the space and file size is a good though except for the paradox mentioned above.
DSig
David Tod Sigafoos ~ SigSOlutions
[email protected] cis:70302,77 voice:503-639-8080
At 28 MAR 1998 08:56AM David Pociu wrote:
Not quite. I think Win95 "cheats" with that one. This is a path I get for the executable of Paint:
C:\PROGRA~1\ACCESS~1\MSPAINT.EXE
As you can see, 8.3 format and no spaces.
At 28 MAR 1998 04:13PM David Pociu wrote:
David,
Here's how you can fix the reference to the Winword executable so it has no spaces in it:
1. Open Windows Explorer
2. Go to View, then Options
3. Click on the File Types tab
4. Find and double-click on Microsoft Word Document
5. Highlight the Open command (should be the default) and double-click on it.
6. In the "Application used to perform action" field, modify the path so it's in 8.3 format (Ex: C:\Progra~1\Office\Winword.exe /n instead of C:\Program Files\Office\Winword.exe /n )
After this, as long as the path to the document is in 8.3 format, it will work every time.
And hopefully OI 3.7 (I think it might be too late for 3.6) will allow for the use of Win95 directories in Utility("RUNWIN" )
Good luck
At 29 MAR 1998 04:27PM DSig (SigSolutions) wrote:
Dave,
Thanks for the note but I don't think I can deliver an app to new users and have them go through that.
I have, as mentioned earlier, created a work around. But as with all work arounds this needs to be corrected. Or at least it would seem so.
DSig
David Tod Sigafoos ~ SigSolutions
[email protected] cis:70302,77 voice:503-639-8080
At 30 MAR 1998 10:54AM David Pociu wrote:
So now we wait and see if 3.7 will address this issue. I'm sure that it will if it's something within OI that can be fixed.
At 30 MAR 1998 03:33PM DSig (SigSolutions) wrote:
I don't know .. I mentioned this several months ago just like the debug in index lookup. The subject died and the last two releases still have the problem .. possibly now that someone else has validated the problem
dsig
David Tod Sigafoos ~ SigSolutions
[email protected] 70302,77 503-639-8080
At 01 APR 1998 02:30PM Cameron Purdy wrote:
dsig,
.. like the debug in index lookup. The subject died and the last two releases still have the problem ..
Doh! If you said something, I completely missed it … will fix el pronto! (Sorry.)
Cameron Purdy
At 02 APR 1998 03:40PM DSig (SigSolutions) wrote:
I said thanks in another response BUT I want to make sure that you understand how much I appreciate your work.
As you know I am more than willing to yell when things are not working right (or as I would like them to) but know that I am more than willing to yell just as loudly when you kids do good work.
dsig
David Tod Sigafoos ~ SigSOlutions
[email protected] cis:70302,77 voice:503-639-8080
At 23 APR 1998 10:57AM Paul Marraffa wrote:
I had a similar problem last year…
Our work around required us to embed single quotes around the path.
Works every time…
At 23 APR 1998 06:12PM David Sigafoos wrote:
Paul,
Not sure what you mean by embedding single quotes but this does work:
rtn=Utility("RUNWIN", "C:\PROGRA~1\MICROS~2\OFFICE\WINWORD.EXE ":ResLoc,"")
where ResLoc is the path information for the file to launch.
The problem is that hardcoding the WINWORD path can be problematic IF the user(s) make any change to the structure for winword. Note that the 'MICROS~2' is named this way because the directory for Microsoft Exchange was removed (which was ~1).
dsig
David Tod Sigafoos ~ SigSOlutions
[email protected] cis:70302,77 voice:503-639-8080
At 23 APR 1998 06:16PM David Sigafoos wrote:
Cameron,
do you know if the RUNWIN problem will be fixed in 3.7 .. AND would it be possible to get a patch now (or as soon as possible) as we are still in 3.5 and are just on the verge of shipping a beta.
We tried hardcoding the path (see my previous note to paul) but problems caused by user removing a program under directory 'microsoft' which caused a change in the ~x count.
dsig
David Tod Sigafoos ~ SigSOlutions
[email protected] cis:70302,77 voice:503-639-8080
At 29 APR 1998 02:46PM Paul Marraffa wrote:
Cameron,
Did we change something in ver 3.6....since the upgrade I have the same problem as David. I used to prefix the command with a char(34) and the winexec converted the path to a 8.3 file name... now it doesn't work ???path=char(34):"c:\program files\microsoft office\office"
program=winword.exe"
doc=99999"
ext=.doc"
Ret_Val=Utility("RUNWIN",path:program:doc:ext,1)
Ret_Val returns a value of the path without executing the code??