Re: do visual basic
Re: do visual basic
- Subject: Re: do visual basic
- From: Paul Berkowitz <email@hidden>
- Date: Wed, 10 Mar 2004 10:19:30 -0800
On 3/10/04 9:49 AM, "Andrew Oliver" <email@hidden> wrote:
>
Regardless of whether the VB Script is valid/executable or not, you still
>
need to assign the result of that script to an AppleScript object if you
>
want to use that value in your AppleScript. I'm sure better VBScripters than
>
I can find the right syntax for returning a value.
You're not paying attention. Andrew. I've written twice that NO, better
VBScripters than you cannot return a value to AppleScript. It can't be done.
The result of 'do Visual Basic' is always 'undefined' in AppleScript.
To get the VB result back, you have to write it to a file that AppleScript
can read. I explained how to do that before you wrote back although you may
not have seen that post yet when you first wrote. You must have it by now.
The here point is that your assumption is wrong. 'do Visual Basic' does not
return any useful result to AppleScript (fourth time now). That's a very big
reason for why a native AppleScript implementation of Word, that works,
would be a great improvement on having to use 'do Visual Basic'.
Nevertheless, the Print# method of writing a string to a file which AS can
read is a serviceable, if awkward, workaround for now.
--
Paul Berkowitz
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.