This content has been marked as final. Show 7 replies
On Fri, 14 Apr 2006 18:24:12 GMT, JP Heidi posted in
> PowerPoint Viewer Cannot find the file "Documents"
> PowerPoint Viewer Cannot find the file "and"
> PowerPoint Viewer cannot find the file "MyFile.pps"
Microsoft applications do not like spaces in file path/names passed via the
command line (which is essentially what Lingo's 'open' command does).
You /may/ be able to enclose the path/name in quotes and use 'open', but I
recommend using Buddy API with it baShortFileName() and baRunProgram() ro
I don't recall whether the free FileXtra4 Xtra has a shortFileName feature,
but it might be worth checking out.
Mark A. Boyd
Where were you yesterday before I went bald????? (actually you probably would have been here had I asked, huh?)
Thanks for the reply. Real quick I just tried:
OK = baOpenFile( the pathName & "Source\MyFile.pps" , "normal" )
and it works.
It seems that this would open the viewer on my PC instead of the CD (in case someone does'nt have PowerPoint installed)
I'll look into the baShortFileName() (what's the difference between this and baOpenFile?) and baRunProgram() (Run PPT Viewer from the CD?) robaShell() functions.
Thanks for your help!
Oh, and it still doesn't explain why Director's "Open" doesn't work all of a sudden . . . new version of PowerPoint, perhaps?
On Fri, 14 Apr 2006 20:05:08 GMT, JP Heidi posted in
> OK = baOpenFile( the pathName & "Source\MyFile.pps" , "normal" )
> and it works.
> It seems that this would open the viewer on my PC instead of the CD (in
> case someone does'nt have PowerPoint installed)
Yes...sort of. It will open the file with whatever program is associated
with the .pps extension - if any. That could be an installed version of
PowerPoint Viewer, the full PowerPoint, Open Office, etc...
> I'll look into the baShortFileName() (what's the difference between
> this and baOpenFile?) and baRunProgram() (Run PPT Viewer from the CD?)
> robaShell() functions.
They're all listed in the Buddy API help file (I meant to type
"...or baShell()" not "...ro baShell()").
Something like this should help illustrate. You might want to include some
baFileExist() functions, etc...
ppViewer = the moviePath &"Source\ppView32.exe"
ppViewer = baShortFileName(ppViewer)
theFile = the moviePath &"Source\MyFile.pps"
theFile = baShortFileName(theFile)
OK = baRunProgram(ppViewer &&theFile, "normal", 0)
if OK < 32 then
-- something went wrong
-- see Buddy Help for return codes
-- alert the user?
baShell() does offer the addition of the WorkDir argument. You may or may
not find that useful for ppt viewer. If there are any externally linked
assets (actions) in the PPS file, the WorkDir might be needed.
Note that 'the pathName' is deprecated and 'the moviePath' is the
recommended replacement - or whatever the equivalent is in MX2004's object
Mark A. Boyd
On Fri, 14 Apr 2006 20:09:03 GMT, JP Heidi posted in
> Oh, and it still doesn't explain why Director's "Open" doesn't work all
> of a sudden . . . new version of PowerPoint, perhaps?
Just guessing, but have you tried it from a projector running in
"C:\Documents and Settings\JP Heidi\Desktop\whatever\" before?
Lingo's 'open' and Microsoft apps have behaved this way as far back as I can
remember. In Director terms, that goes back to Dir 4.0 some time in the 90's.
Some programs will accept QUOTE &"path\to\file.ext" "E, but I don't think
MS apps ever have.
Mark A. Boyd
The answer is quite simple. Everyone is making it too complicated. Your files need to be at the root level of the drive when going to the powerpoint files. The reason it works on the CD is that your CD is the root level. Works everytime.
> Just guessing, but have you tried it from a projector running in
> "C:\Documents and Settings\JP Heidi\Desktop\whatever\" before?
I always test my projectors on my desktop (I cannot run .exe files from my document server). Of course, it's been about 6 months since I did a project like this, so it is very possible that my tired old brain is just getting the best of me.
Swasher1 -- Yes, that is a simple answer and it does work. It is just easier to tell people to copy the files to the desktop rather than try to explain to them what the "C" drive is (I work with some very intelligent engineers ; ) . . . not only that, but people are sometime hesitant to put "strange" files on their hard drive.
Anyway, Buddy seems to be the answer . . . thanks for all your help!!