Hello Paul,

On Jun 7, 2010, at 2:59 AM, Paul Berkowitz wrote:

>
> Yes, that's the right way to do it. Since the new Word scripting  
> (Word 2004,
> improved 2008), you should use the 'save as' terminology in the  
> Microsoft
> Word Suite, rather than the "old" 'save' terminology from the Standard
> Suite, at least when you're doing anything other than a plain  
> 'save' with no
> parameters.
>
> The 'save as' command, like everything else in all suites except  
> Standard,
> is part of a thoroughgoing revision of Word's applescripting, built  
> directly
> upon its OLE Automation underpinnings, that mirrors the Visual Basic
> language which was always better functioning than the old  
> AppleScript model.
> They kept the Standard Suite, or much of it, I guess to make people
> unfamiliar with the more complicated (and contorted) new model more
> comfortable. But it doesn't work any better than it ever did, and  
> perhaps
> worse. (Also, I'm not sure, but I think that the 'as file  
> specification'
> thing that John mentions may have been deprecated in newer OS's, or  
> at least
> Word's hooks into it no longer work. But that's a separate issue.)
>
> What it comes down to is that the 'as' [type] parameter with the  
> 'save'
> command does not work as advertised, whereas the 'file format'  
> parameter,
> and all the other parameter, supplied with the 'save as' command in  
> the MS
> Word Suite, works just fine. Stick with that.

Thank you for the explanation. The way the "Dictionary" is presented  
is really confusing. I was happy to find the right way to go.

Thank you again.

Best regard,

Nobumi Iyanaga
Tokyo,
Japan