Mitrokhin wrote:
> No I havn't, see, my use of macros in word just might be very
> idiosyncratic and then there's the question about coding quality: i'm
> pretty far from being a programming whiz but you be the judge, would
> eg. these hold an interest for other people (beware of linebreaks) ?
>> 1. Toogle highlight on the selection or the whole line. Chose among
> some predetermined highlightcolors.
>
> 2. Find the first occurence of a specially named bookmark from the
> current ip to the end of the doc (if found go to said bookmark and
> delete it) OR insert a bookmark at the current ip and highlight the
> selection/line.
>

Yeah, I'm no programming whiz to be judging quality either. And yeah,
my macros are all very idiosyncratic too. But I might wind up borrowing
your highlight script at some point, or building on it.

I probably won't link them from the page, but by posting them here they
should come up if anyone searches the group for AppleScript. Any code
sample that works might be useful for someone.

Thanks,
Daiya

Phillip Jones wrote:

[..]
>
> I don't need or want a 50 page explanation. Just why is it so complicated.
>
> VBA support for Mac Office products have been in all versions for me
> back to Excel 5 and Word 6 days. In fact it was so closely matched that
> nasty bugs that could destroy files and hard drives on a PC could do the
> same thing, on a Mac. Reason why it was recommend to turn off VBA based
> Macros by Virus detection software vendors such a Symantec, as far back
> as Word 6 days.
>

Hi Phillip,

The PC version of VBA is designed to use Microsoft Windows. The Windows
operating system addresses the hardware in specific ways. Since Windows
is not on a Mac, VBA will have to be customized to take advantage of
MacOS and how Apple hardware is controlled by software.

It's not just the mapping of commands and keyboard shortcuts. Everything
including window management and the way the screen is drawn is different
on a Mac than a PC. Normally, software is written in something like C++
or C#, then it is converted to low level programs. VBA sometimes has to
interface directly with the hardware to maintain speed (something
notably lacking in previous Mac iterations of VBA).

Whenever you use software that you didn't write yourself you are
trusting the author to not damage your system. No matter what language
is used, as long as it has access to the file system it has the
potential to do bad things. The absolute safest thing to do is to not
run any software at all on your computer. That's downright stupid. It's
equally stupid to brand all software written in a given language as too
dangerous to use and then ban it or bad mouth it. Also stupid is running
any and all software the comes your way regardless of its source.

There are tens of thousands of viruses and other exploits. The vast
majority deal with internet and web technologies, especially web
browsers and email.

I only know of one VBA virus, the ancient Word Macro virus, which was
easy to get rid of simply by deleting the file Normal.dot. There may
have been a couple other viruses written in VBA, but it is hardly
something to get all flustered about.

Having the full file system at the developer's finger tips is a very
valuable thing. Almost every application I write needs to save, open,
and revise documents, so this is essential even though it could be used
in bad ways.

-Jim

i microsoft.public.mac.office.word skrev Daiya Mitchell
Mon, 19 May 2008 19:27:49 -0400 (-), i en artikel med
ID <uUSzyfguIHA.420>
og titlen "Re: VBA to return in the next version of Office Mac !?",
følgende:

:
: Yeah, I'm no programming whiz to be judging quality either. And yeah,
: my macros are all very idiosyncratic too. But I might wind up borrowing
: your highlight script at some point, or building on it.
:

Great

: I probably won't link them from the page, but by posting them here they
: should come up if anyone searches the group for AppleScript. Any code
: sample that works might be useful for someone.
:
: Thanks,
: Daiya
: >
:

And thank you for your "Script Solutions for Word 2008" and
"Using MS Word" pages :)

In article <uxcV77PuIHA.4376>,
Phillip Jones <pjones1> wrote:

> I'm just say MS has never had a True two year delivery date.

MacWord/Office:

Version Year
1 1985
3 1987
4 1989
5 1991
6 1993
98 1998
01 2000
vX 2001
04 2004
08 2008

Hit the two-year mark: 5 out of 9 times

WinWord/Office
1 1989
2 1991
6 1993
95 1995
97 1997
00 1999
02 2001
03 2003
07 2006

Hit the two-year mark: 7 out of 8 times.