Re: AppleScript and VBA
Re: AppleScript and VBA
- Subject: Re: AppleScript and VBA
- From: Paul Berkowitz <email@hidden>
- Date: Wed, 09 Jan 2002 21:07:59 -0800
On 1/9/02 1:24 PM, "Jon Pugh" <email@hidden> wrote:
>
At 12:13 PM +1100 1/9/02, Dale Gillard wrote:
>
> So it seems that Adobe must have licensed VBA too and incorporated it into
>
> inDesign and Illustrator.
>
>
Not necessarily.
>
>
It turns out that you only need a license if you want to ship the development
>
runtime that allows you to edit VBA in your app. If you make them purchase
>
VBA separately, then you don't need to license VBA or bow to Redmond.
>
>
Neither InDesign nor Illustrator ship with VBA. They are merely scriptable
>
via VBA if you happen to purchase it separately.
>
Jon,
Do you really mean VBA, or VB Editor? Can you only script the apps in VBA if
VBA has already been "implemented" in them? Otherwise how exactly do you
install VBA "in" the applications when you purchase it separately?
VBA doesn't have tell blocks like AppleScript, but seems to "belong" to the
application running the VB Editor in use. In MS Word, for example,
'Application.' (which never needs to be stated explicitly) means Word
itself. But you can set and 'Dim' variables to new, separate instances of
Word, and to Word objects such as Documents. You can also Dim variables to
instances of MS Excel, or any app with VBA, from the VB Editor in Word.
Does this mean that you could script InDesign or Illustrator from the VB
Editor in Word the same way? Or would you first need to somehow "add" VBA to
InDesign or Illustrator, like the VBA 1.1 file that sits in the Office
subfolder? That's the part I don't get. If you already own VBA in MS Office,
and have the Editor there already, do you have everything you need?
--
Paul Berkowitz