| Thanks, Paul -- That worked!
On Jan 3, 2014, at 10:43 PM, Paul Berkowitz wrote: It may be that be using a file, you're actually forcing the Finder to try to open it, leading to the same problem you get when you try to double-click it. What happens if you do this:
set colonPath to (POSIX file "/Users/berkowitz/Documents/Documents/musicale - t&g/performance class") as text
tell application "Microsoft Word" to open file name colonPath
Word opened the file. And that solves my problem. Thank you.
On a related topic...
Why POSIX file? (Are you dragging the file to AppleScript Editor which shows its POSIX path?)
Yes. I didn't think it mattered.
Word actually takes a colon-separated path, and prefers it to an actual file, especially if you use the 'file name' paramater as found in the Word dictionary..
Oh! I see! Thanks for the explanation.
You haven't said what OS you're ion.
I'm afraid I can't reproduce this in OS 10.9.1 with Word 2008 12.3.6, so I can't test a solution.
I'm also using Word 2008 for Mac 12.3.6, but on MacOS 10.6.8. I suppose you may not have old Word files that are that old. No matter -- shortly, neither will I!
Thanks very much, Paul, for your insight. I would never have figured that out on my own.
--Gil
On Jan 3, 2014, at 10:43 PM, Paul Berkowitz wrote:
On 1/3/14, 4:29 PM, "Gil Dawson" <email@hidden> wrote:
Using Microsoft Word:Mac 2008 Version 12.3.6,
I just noticed that Word will no longer open my (hundreds of) old Word documents just by double-clicking their icons in the Finder.
Instead, Word puts up an alert:
<FileName> uses a file type that is blocked
from opening In this version.
To help secure your computer, some file types are
blocked Irom opening when you double-click the file or
drag the file to the Microsoft Word Icon. If you trust that
this file Is secure, you can open the file by clicking Open
on the File menu.
You haven't said what OS you're ion.
I'm afraid I can't reproduce this in OS 10.9.1 with Word 2008 12.3.6, so I can't test a solution. But what surprises me about your attempt to do this by script is this line:
set aFile to POSIX file "<path to an archived Microsoft Word 1.x-5.x document>"
tell application "Microsoft Word" to open aFile
Why POSIX file? (Are you dragging the file to AppleScript Editor which shows its POSIX path?) Word actually takes a colon-separated path, and prefers it to an actual file, especially if you use the 'file name' paramater as found in the Word dictionary.. It may be that be using a file, you're actually forcing the Finder to try to open it, leading to the same problem you get when you try to double-click it. What happens if you do this:
set colonPath to (POSIX file "/Users/berkowitz/Documents/Documents/musicale - t&g/performance class") as text
tell application "Microsoft Word" to open file name colonPath
As I say, I have no problem with either version, so I can't test if it will help you. But give it a try.
--
Paul Berkowitz
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden
|